A service processing system, method, apparatus, electronic device, and storage medium

Abstract

The present disclosure relates to the technical field of computer, and provides a service processing system, method, device, electronic equipment and storage medium. The system comprises a UNISYS host system, a MATIP gateway, an ESB in an SOA architecture and an open system; the gateway bridges the host system and the ESB, detects and loads configuration information of a host service, defines and saves a corresponding relationship between a host service name and grouped link resources according to grouping information of the link resources, and creates metadata corresponding to the host service; a MATIP connection is created according to the grouped link resources; attribute information of the host service is constructed according to the metadata corresponding to the host service and in combination with node information and a service interface of the gateway; and service registration is completed by calling a service directory interface of the SOA architecture through the ESB. By constructing the gateway, the grouped link between the gateway and the host system is used to abstractly map the corresponding service in the host, so that the service definition and publication of the host service in the open system are proxied.

Description

TECHNICAL FIELD

[0001] The present disclosure belongs to the technical field of computers, and particularly relates to a service processing system, method and device, electronic equipment and storage medium. BACKGROUND

[0002] Under the background of globalization, as an important part of international trade, air logistics has become an important support for the economic development of a country. Early civil aviation information systems mostly use UNISYS large mainframe systems, which use private protocols internally and centrally process all business requirements. When interacting with external airlines and GDS (Global Distribution System), the mainframe system needs to follow the standard MATIP (Mapping of Airline Reservation, Ticketing and Messaging Traffic over IP) protocol for data interaction. The MATIP protocol is an end-to-end TCP network transmission encapsulation of aviation-specific protocol data packets, which establishes a routing-independent mapping standard between the transmission layer and aviation applications.

[0003] With the rapid increase in civil aviation business models and processing capacity, the centralized processing of business by large mainframe systems has become a bottleneck restricting the development of civil aviation business informatization. More and more businesses are moving to open and distributed systems. In the migration process, in the face of numerous interaction requirements between open systems and mainframe systems, how to solve the service processing of mainframe services in open system architecture, such as service definition and publication, fault isolation, protocol adaptation and monitoring management, and realize reliable and stable data interaction between mainframe services and open services has become an important problem in the business transfer process.

[0004] SOA (Service-Oriented Architecture) divides daily business applications into individual business function services and processes, and associates these services through well-defined interfaces and standard protocols. Based on the loose coupling between services in the SOA architecture, users can build, deploy and integrate services without relying on application programs and their running platforms, thereby improving the flexibility of business processes, accelerating development speed and reducing development costs.

[0005] Currently, there is no service processing system that can implement various types of mainframe services in an open SOA architecture. To support business interaction between mainframe services and open services, it is necessary to implement service processing of various types of mainframe services in an open SOA architecture. Therefore, a service processing system, method, device, electronic equipment and storage medium are needed. SUMMARY

[0006] To solve the above problems, the disclosure provides a service processing system, method, device, electronic equipment and storage medium, which realizes service processing such as service publishing of host services in the SOA architecture by grouping and service definition of the MATIP link.

[0007] In a first aspect, a service processing system is provided, and the system comprises: a UNISYS host system, a MATIP gateway, an ESB in an SOA architecture, and an open system; wherein the MATIP gateway bridges the UNISYS host system and the ESB in the SOA architecture.

[0008] The UNISYS host system is configured to provide host services.

[0009] The MATIP gateway is configured to detect and load configuration information of the host services, define and save a correspondence between a host service name and grouped MATIP link resources according to grouping information of the MATIP link resources in the configuration information, create metadata corresponding to the host services, create MATIP connections in sequence according to the grouped MATIP link resources, construct attribute information of the host services based on the metadata corresponding to the host services and in combination with node information and service interfaces of the MATIP gateway, and complete service registration by calling a service directory interface of the SOA architecture through the ESB based on the attribute information of the host services.

[0010] The ESB is configured to connect the open system, provide a service directory, and perform protocol conversion and message routing.

[0011] The open system is configured to provide open services.

[0012] Further, the MATIP gateway is further configured to monitor changes in MATIP link resource information, start a new MATIP connection when a new MATIP link resource is added, add the new MATIP connection to grouped MATIP link resources corresponding to a host service name, terminate a MATIP connection corresponding to a deleted MATIP link resource when the MATIP link resource is deleted, and remove the MATIP link resource from MATIP link grouping resources of a corresponding host service, and provide host service state query based on a state of the grouped MATIP link.

[0013] Further, the MATIP gateway is specifically configured to, when it is queried that a host service is available, complete service registration by calling a service directory interface of the SOA architecture through the ESB based on attribute information of the host service.

[0014] Further, the MATIP gateway is further configured to, when it is queried that a host service is unavailable or a quit signal is received, complete service deregistration by calling a service directory interface of the SOA architecture through the ESB.

[0015] Further, the MATIP gateway is further configured to determine the state of the ESB node based on a result of probing the IP address and service port of the ESB node; and / or determine the state of the ESB node based on a result of transmitting and receiving the message in the service request message, wherein the state of the ESB node is available or unavailable.

[0016] Further, the host system comprises a host service processing node; and the open system comprises an open service processing node.

[0017] The open service processing node is configured to send an open service request message carrying a target host service name to the ESB; and receive an open service response message.

[0018] The ESB is configured to find a MATIP gateway address corresponding to a service name matched with the target host service name from a service directory, send the open service request message by using the found MATIP gateway address; and receive and forward the open service response message to the open service processing node.

[0019] The MATIP gateway is further configured to receive the open service request message, acquire a MATIP link list corresponding to the target host service name carried in the open service request message by using the saved correspondence between the host service name and the group MATIP link resource, select a MATIP link from the acquired MATIP link list, forward the open service request message to the target host service processing node by using the selected MATIP link; and receive the open service response message, and send the open service response message to the ESB.

[0020] The host service processing node is configured to receive the open service request message sent by the MATIP gateway, process the open service request message, obtain the open service response message, and send the open service response message to the MATIP gateway.

[0021] Further, the MATIP gateway is specifically configured to select a MATIP link from the acquired MATIP link list according to a load balancing strategy and a MATIP link state.

[0022] Further, the host system comprises a host service processing node; and the open system comprises an open service processing node, and the ESB is composed of a plurality of ESB nodes.

[0023] The host service processing node is configured to send a host service request message carrying a target open service name to the MATIP gateway; and receive a host service response message.

[0024] The MATIP gateway is further configured to receive a host service request message, determine a target ESB node based on a target open service name and cached ESB node information, send the host service request message to the target ESB node, and receive and forward a host service response message to a host service processing node.

[0025] The ESB node is configured to receive a host service request message, find a service name matching the target open service name from a service directory, determine an open service processing node providing the target open service, send the host service request message to the determined open service processing node, and receive and forward a host service response message to the MATIP gateway.

[0026] The open service processing node is configured to receive a host service request message sent by the ESB node, process the host service request message to obtain a host service response message, and send the host service response message to the ESB node.

[0027] Further, the MATIP gateway is further configured to perform protocol and data format adaptation on the request message and the response message before forwarding, wherein the host service request message and the open service response message are adapted in protocol and data format by using an ESB internal TCP-based enterprise private protocol, and the host service response message and the open service request message are adapted in protocol and data format by using MATIP.

[0028] In a second aspect, a service processing method is provided, and the method comprises:

[0029] detecting and loading configuration information of a host service, the configuration information comprising grouping information of MATIP link resources between a MATIP gateway and a host system;

[0030] defining and saving a correspondence between a host service name and grouped MATIP link resources according to the grouping information of the grouped MATIP link resources, and creating metadata corresponding to the host service;

[0031] creating MATIP connections in sequence according to the grouped MATIP link resources;

[0032] constructing attribute information of the host service according to the metadata corresponding to the host service and in combination with node information and service interfaces of the MATIP gateway;

[0033] based on the attribute information of the host service, calling an SOA architecture service directory interface through the ESB, so that the SOA architecture service directory interface writes the attribute information of the host service into a service directory, and completes service registration.

[0034] Further, the method further comprises:

[0035] Monitoring the change of the MATIP link resource information;

[0036] In the case of addition, a new MATIP connection is initiated and added to the MATIP link resource corresponding to the group of the host service name; in the case of deletion, the MATIP connection corresponding to the deleted MATIP link resource is terminated and removed from the MATIP link group resource corresponding to the host service;

[0037] Providing a host service state query according to the state of the group MATIP link.

[0038] Further, the method further comprises:

[0039] Before calling the SOA architecture service directory interface through the ESB based on the attribute information of the host service, the method further comprises:

[0040] Determining that the host service is available.

[0041] Further, it is characterized in that,

[0042] When the host service is queried to be unavailable or a quit signal is received, the SOA architecture service directory interface is called through the ESB so that the SOA architecture service directory interface removes the attribute information of the host service from the service directory, completing service deregistration.

[0043] Further, it is characterized in that, the method further comprises:

[0044] Based on the detection result of the IP address and service port of the ESB node, the state of the ESB node is determined; and / or based on the result of sending and receiving the message in the service request message, the state of the ESB node is determined, wherein the state of the ESB node is available or unavailable.

[0045] Further, the method further comprises:

[0046] Receiving an open service request message;

[0047] Using the saved correspondence between the host service name and the group MATIP link resource, the MATIP link list corresponding to the target host service name carried in the open service request message is obtained;

[0048] Selecting a MATIP link from the obtained MATIP link list, and forwarding the open service request message to the target host service processing node using the selected MATIP link;

[0049] Receiving an open service response message, and sending the open service response message to the ESB.

[0050] Further, selecting a MATIP link from the acquired MATIP link list, specifically comprising:

[0051] According to the load balancing strategy and the MATIP link state, selecting a MATIP link from the acquired MATIP link list.

[0052] Further, the method further comprises:

[0053] Receiving a host service request message carrying a target open service name;

[0054] Based on the target open service name and the cached ESB node information, determining a target ESB node;

[0055] Sending the host service request message to the target ESB node;

[0056] Receiving and forwarding a host service response message from the ESB node to the host service processing node.

[0057] Further, the method further comprises:

[0058] Before forwarding the request message and the response message, performing protocol and data format adaptation, wherein, for the host service request message and the open service response message, using an ESB internal TCP-based enterprise private protocol to perform protocol and data format adaptation; for the host service response message and the open service request message, using MATIP to perform protocol and data format adaptation.

[0059] In a third aspect, a service processing device is provided, characterized in that the device comprises a configuration management module, a link management module and a proxy publishing module; wherein:

[0060] The configuration management module is configured to detect and load configuration information of the host service, the configuration information comprising grouping information of MATIP link resources between the MATIP gateway and the host system;

[0061] The link management module is configured to define and save a correspondence between the host service name and the grouped MATIP link resources according to the grouping information of the grouped MATIP link resources, create metadata corresponding to the host service, and create MATIP connections in sequence according to the grouped MATIP link resources.

[0062] The proxy publishing module is configured to construct attribute information of the host service according to the metadata corresponding to the host service, in combination with node information and service interfaces of the MATIP gateway, and invoke a SOA architecture service directory interface based on the attribute information of the host service, so that the SOA architecture service directory interface writes the attribute information of the host service into a service directory, and completes service registration.

[0063] Further, the link management module is further configured to monitor changes in the MATIP link resource information; when a MATIP link resource is added, initiate a new MATIP connection, and add the new MATIP connection to the MATIP link resource corresponding to the service name of the host; when a MATIP link resource is deleted, terminate the MATIP connection corresponding to the deleted MATIP link resource, and remove the MATIP link resource from the MATIP link group resource corresponding to the host service; and provide a host service state query according to the state of the MATIP link group.

[0064] Further, the device further comprises a proxy publishing module, which is configured to query the link management module based on the attribute information of the host service before calling the SOA architecture service directory interface through the ESB, and query that the host service is available.

[0065] Further, the link management module is further configured to trigger the proxy publishing module when it is queried that the host service is unavailable or a quit signal is received.

[0066] The proxy publishing module is further configured to call the SOA architecture service directory interface through the ESB under the triggering of the link management module, so that the SOA architecture service directory interface removes the attribute information of the host service from the service directory, and completes service deregistration.

[0067] Further, the device further comprises:

[0068] A node alive detection module is configured to determine the state of the ESB node based on the detection result of the IP address and service port of the ESB node, and / or determine the state of the ESB node based on the result of sending and receiving a message in a service request message, wherein the state of the ESB node is available or unavailable.

[0069] Further, the device further comprises:

[0070] A data forwarding module is configured to receive an open service request message, select a MATIP link from the obtained MATIP link list, and forward the open service request message to a target host service processing node using the selected MATIP link; and receive an open service response message and send the open service response message to the ESB.

[0071] A link management module is configured to obtain a MATIP link list corresponding to a target host service name carried in an open service request message using the correspondence between the saved host service name and the MATIP link resource.

[0072] Further, the data forwarding module is specifically configured to select a MATIP link from the obtained MATIP link list according to a load balancing strategy and the state of the MATIP link.

[0073] Further, the device further comprises:

[0074] The data forwarding module is further configured to receive a host service request message, determine a target ESB node based on the target open service name and the cached ESB node information, send the host service request message to the target ESB node, and receive and forward a host service response message from the ESB node to the host service processing node.

[0075] Further, the data forwarding module is further configured to perform protocol and data format adaptation on the request message and the response message before forwarding, wherein the host service request message and the open service response message are adapted in protocol and data format by using an ESB internal TCP-based enterprise private protocol, and the host service response message and the open service request message are adapted in protocol and data format by using MATIP.

[0076] In a fourth aspect, an electronic device is provided, comprising at least one processor and at least one storage medium electrically connected; the storage medium is connected to the processor by a bus; wherein,

[0077] The storage medium stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the service processing method described above.

[0078] In a fifth aspect, a computer storage medium is provided, the storage medium stores instructions executable by at least one processor; the instructions are executed by the at least one processor to enable the at least one processor to perform the service processing method described above.

[0079] Compared with the prior art, the present disclosure has the following advantages:

[0080] 1. By constructing a MATIP gateway, the corresponding services in the host are abstracted by using the packet MATIP link between the MATIP gateway and the host system, so as to proxy the service definition and publication of the host service in the open system;

[0081] 2. Through the management and maintenance of the packet MATIP link, the service management functions such as upgrade and maintenance, traffic protection, service routing, load balancing, isolation and recovery of the host service in the open system are realized;

[0082] 3. The MATIP gateway realizes the conversion between the format adopted by the host service and the data format adopted by the open service; in the adaptation of the communication protocol, the MATIP gateway is used as a MATIP client to connect the UNISYS host service, and is used as a client of the ESB to connect the ESB node by using the enterprise internal private protocol. The host system and the ESB in the SOA architecture do not need to increase any adaptation, and there is no invasiveness to the existing host system and the open system.

[0083] Other features and advantages of the present disclosure will be set forth in the description that follows, and in part will be apparent from the description, or can be learned by practice of the present disclosure. The purposes and other advantages of the present disclosure will be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings. BRIEF DESCRIPTION OF DRAWINGS

[0084] In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present disclosure, and those skilled in the art can obtain other drawings according to these drawings without creative effort.

[0085] Figure 1 A logical schematic diagram of a service publishing system according to an embodiment of the present disclosure is shown;

[0086] Figure 2 A service publishing and updating process flowchart schematic diagram of a host service under an SOA architecture according to an embodiment of the present disclosure is shown;

[0087] Figure 3 An SOA open service request UNISYS host service data interaction schematic diagram according to an embodiment of the present disclosure is shown;

[0088] Figure 4 A UNISYS host service request SOA open service data interaction schematic diagram according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0089] In order to make the purposes, technical solutions and advantages of the embodiments of the present disclosure clearer, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are some of the embodiments of the present disclosure, but not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by those skilled in the art without creative effort fall within the scope of the present disclosure.

[0090] In the face of the technical diversification of business systems, the difficulty of transforming legacy systems, and other issues, in order to reduce the complexity and coupling degree of system interaction, an ESB (Enterprise Service Bus, enterprise service bus) implementation solution is usually used. The narrow sense of ESB is a pipeline used to connect various service nodes. In order to integrate services of different systems and different protocols, focus on message conversion, protocol adaptation and routing work, realize the interconnection of different services, and undertake the role of interactive services. The broad sense of ESB extends the scope to management services and process services, and provides functions such as service directory management, runtime monitoring and service aggregation.

[0091] In the process of civil aviation business opening, the open system usually adopts SOA architecture for deployment, and uses ESB to integrate various open services of different protocols. In the civil aviation mainframe system, each externally published mainframe service needs to have a set of MATIP resources, which are used to establish a connection with external systems for data exchange. The gateway is an important bridge connecting the local network and the external network, and can realize smooth communication between the two networks. Therefore, the combination of the two can publish the mainframe service in the service directory in the SOA architecture through the gateway via the ESB. From the perspective of the open system, a set of MATIP links corresponds to a mainframe service, so the governance of a certain mainframe service under the SOA architecture can be converted into the governance of the MATIP link corresponding to the service.

[0092] Based on the above analysis, the present disclosure proposes a service processing method for implementing mainframe services in an open system, which mainly includes service publishing and governance. By constructing a MATIP gateway, the corresponding service in the mainframe is abstracted and mapped by using the packet MATIP link between the MATIP gateway and the mainframe system, so as to proxy the service definition and publishing of the mainframe service in the open system; and by managing and maintaining the packet MATIP link, the service governance functions of the mainframe service in the open system, such as upgrade and maintenance, traffic protection, service routing, load balancing, isolation and recovery, are realized.

[0093] The mainframe service in the present disclosure can specifically be a mainframe service in a civil aviation UNISYS mainframe system.

[0094] Figure 1 A logical schematic diagram of a service publishing system according to one of the embodiments of the present disclosure is shown, as shown in Figure 1 The service publishing system of the embodiment of the present disclosure includes: a UNISYS mainframe system, a MATIP gateway, an ESB in an SOA architecture, and an open system; wherein the MATIP gateway is newly added and used to bridge the mainframe system and the ESB in the open system.

[0095] The MATIP gateway is used for proxying the host service (a business processing unit in a UNISYS host system) to service publishing in the SOA architecture, providing support for interaction between the host system and the open system, and realizing business interconnection between the host system and the open system.

[0096] The ESB is used for providing a service directory, performing protocol conversion and message routing.

[0097] The MATIP gateway comprises a configuration management module, a proxy publishing module, a link management module, a node alive detection module, a protocol adaptation module and a data forwarding module, wherein:

[0098] The configuration management module is used for grouping MATIP resources, maintaining a mapping relationship with the host service, storing routing, flow control, data conversion and other rules between the host service and the open service, and realizing dynamic management of configuration items.

[0099] The proxy publishing module is used for realizing publishing and updating of the host service in the service directory of the SOA architecture, so as to support addressing of the host service by the service bus ESB under the SOA architecture.

[0100] The link management module is used for creating and maintaining the MATIP link with the host service, realizing isolation and recovery of the host node, and providing host service state query to the proxy publishing module and the data forwarding module according to the state of the grouped MATIP link. When there is an available MATIP link in the grouped MATIP link, the state of the host service is available, and when there is no available MATIP link in the grouped MATIP link, the state of the host service is unavailable.

[0101] The node alive detection module is used for detecting the alive state of the ESB node of the SOA architecture, realizing isolation and recovery mechanism of the ESB node, and providing support for routing decision in the data forwarding process.

[0102] The protocol adaptation module is used for realizing bidirectional conversion between the MATIP used in the host system and the TCP-based enterprise private protocol inside the ESB.

[0103] The data forwarding module is used for receiving the SOA request message from the ESB service bus, forwarding it to the target host service, selecting the target node according to the routing, load balancing and flow control rules, and completing message conversion by using the function provided by the protocol adaptation module.

[0104] In the above modules:

[0105] The configuration management module is one of the background tasks of the MATIP gateway, and provides a management function of gateway configuration items. Through management of MATIP resources between the gateway and the host service, the agent publishing module is provided with basic attribute information of the service to be published, and the link management module is provided with metadata for creating a MATIP link. When the service management related rules change, the gateway cache is updated in a timely manner, thereby providing a basis for processing of other modules.

[0106] The agent publishing module aims to solve the service publishing of the host service in the SOA architecture deployment. The agent publishing module obtains the group MATIP link corresponding to a host service from the configuration management module, obtains the service state corresponding to the group MATIP link from the link management module, and initiates service information updating to the SOA service directory.

[0107] The node alive detection module can specifically implement active and passive mechanisms for health check. In the active check mechanism, the state of the ESB node is updated through periodic detection of the ESB node IP and service port, for example, three consecutive successful / failure times are considered as the healthy / unhealthy state of the ESB node. In the passive check mechanism, the health / unhealth state count value of the ESB node is updated when the data is sent or received successfully / failure, and if the count value reaches a certain threshold, the state of the ESB node is considered as healthy / unhealthy.

[0108] The MATIP gateway bridges the host service and the ESB under the SOA architecture, and the protocol adaptation module implements adaptation and conversion of different communication protocols and data formats, so that the existing deployment and service do not need to additionally increase new adaptation components, and the UNISYS host system and the open system are not invasively used. In the UNISYS host service process of the SOA service request message, the SOA service sends the request message to the service bus ESB. Since the MATIP gateway uses the node information of the MATIP gateway as the node information of the micro-service instance when publishing the service of the agent host service under the SOA architecture, the ESB sends the request message to the MATIP gateway. The data forwarding module selects the corresponding MATIP link group according to the destination service name in the request message, selects the node to be forwarded according to the link state and load balancing decision, and uses the protocol adaptation module function to complete the message conversion and data forwarding.

[0109] The above describes the functions of the newly added MATIP gateway, and the functions of the service processing system in the embodiment of the present disclosure are described below.

[0110] The UNISYS host system is configured to provide a host service.

[0111] The MATIP gateway is configured to detect and load configuration information of a host service, define and save a correspondence between a host service name and grouped MATIP link resources according to grouping information of the MATIP link resources in the configuration information, create metadata corresponding to the host service, create MATIP connections in sequence according to the grouped MATIP link resources, construct attribute information of the host service according to the metadata corresponding to the host service and in combination with node information and service interfaces of the MATIP gateway, and complete service registration by calling a SOA architecture service directory interface through an ESB based on the attribute information of the host service.

[0112] The ESB is configured to connect open systems, provide a service directory, and perform protocol conversion and message routing.

[0113] The open system is configured to provide open services.

[0114] The above system achieves service publishing of a host service in a SOA architecture.

[0115] Further, the MATIP gateway is further configured to monitor changes in MATIP link resource information, start a new MATIP connection when the MATIP link resource information is added, add the new MATIP connection to grouped MATIP link resources corresponding to a host service name, terminate a MATIP connection corresponding to a deleted MATIP link resource when the MATIP link resource information is deleted, and remove the MATIP link resource from MATIP link grouped resources corresponding to the host service, and provide a host service state query according to a state of the grouped MATIP link.

[0116] Further, the MATIP gateway is specifically configured to, when it is found that a host service is available, complete service registration by calling a SOA architecture service directory interface through an ESB based on attribute information of the host service.

[0117] Further, the MATIP gateway is further configured to, when it is found that a host service is unavailable or a quit signal is received, complete service deregistration by calling a SOA architecture service directory interface through an ESB.

[0118] Further, the MATIP gateway is further configured to determine a state of an ESB node based on a detection result of an IP address and a service port of the ESB node, and / or determine the state of the ESB node based on a result of sending and receiving a service request message, where the state of the ESB node is available or unavailable.

[0119] Further, the host system includes a host service processing node, the open system includes an open service processing node, and the ESB is composed of a plurality of ESB nodes.

[0120] The open service processing node is configured to send an open service request message carrying a target host service name to the ESB; and receive an open service response message;

[0121] The ESB is configured to search the service directory for a MATIP gateway address corresponding to a service name that matches the target host service name, send an open service request message using the found MATIP gateway address, and receive and forward an open service response message to an open service processing node.

[0122] The MATIP gateway is further configured to receive an open service request message, obtain a MATIP link list corresponding to a target host service name carried in the open service request message using a stored correspondence between host service names and grouped MATIP link resources, select a MATIP link from the obtained MATIP link list, and forward the open service request message to a target host service processing node using the selected MATIP link; and receive an open service response message and send the open service response message to the ESB.

[0123] The host service processing node is configured to receive an open service request message sent by the MATIP gateway, process the open service request message, obtain an open service response message, and send the open service response message to the MATIP gateway.

[0124] Furthermore, the MATIP gateway is specifically configured to select a MATIP link from the acquired MATIP link list according to a load balancing policy and a MATIP link status.

[0125] Further, the host system includes a host service processing node; the open system includes an open service processing node;

[0126] The host service processing node is configured to send a host service request message carrying a target open service name to the MATIP gateway; and receive a host service response message;

[0127] The MATIP gateway is further configured to receive a host service request message, determine a target ESB node based on the target open service name and cached ESB node information, send the host service request message to the target ESB node, and receive and forward a host service response message to the host service processing node.

[0128] The ESB node is configured to receive a host service request message, search a service directory for a service name that matches a target open service name, determine an open service processing node that provides the target open service, send the host service request message to the determined open service processing node; and receive and forward a host service response message to a MATIP gateway;

[0129] The open service processing node is configured to receive a host service request message sent by the ESB node, process the host service request message, obtain a host service response message, and send the host service response message to the ESB node.

[0130] The above embodiment describes the service processing system function in the present disclosure, and the service processing scheme of the present application is described below through a specific embodiment.

[0131] In view of the fact that the host system complies with the standard MATIP protocol when interacting with external systems, each host service uses one or more MATIP links to concurrently process service request messages, therefore, in the implementation of the MATIP gateway, the corresponding service in the host is abstracted by using the packet MATIP link between the gateway and the host, the service definition of the host service under the open architecture is performed, the maintenance management of the service mapping is performed by the configuration management module, the service publishing of the host service under the open SOA architecture is completed by using the proxy module, and the service state updating of the host service in the open SOA architecture is implemented by using the link state information provided by the link management module during the service running process.

[0132] The service publishing and updating process of a host service under the SOA architecture is shown in Figure 2 The implementation steps are as follows:

[0133] Step 1. The configuration management module loads the configuration information when detecting that the configuration information has changed.

[0134] The configuration information includes MATIP link resource grouping information, ESB node information, and system control parameters such as detection interval, and in this scenario, the configuration information involved in the change refers to the MATIP link resource grouping information, which includes the host service name, the host node IP and port, the MATIP resource used for open system interaction, and the maximum message length supported by the service.

[0135] Step 2. The configuration management module defines the corresponding relationship between the newly added host service S0 and the MATIP resource R0 according to the grouping information of the MATIP resource, and creates the metadata M0 corresponding to the host service S0.

[0136] Step 3. The configuration management module loads the service governance rules of the host service S0 to the gateway cache for use by the protocol conversion module and the data forwarding module in the data processing link.

[0137] Step 4. The link management module creates MATIP connections according to the MATIP resource R0 of the host service S0, and creates multiple MATIP connections if R0 is multiple MATIP resources, and then enters the MATIP connection maintenance state.

[0138] Step 5. The link management module calls the link management module interface to inquire whether the state of the host service S0 has changed. The state of the host service S0 is determined by the connection state in the MATIP resource R0. If all connections in the resource R0 are in the unavailable state, the state of the host service S0 is unavailable. If there is a connection in the available state, the state of the host service S0 is available. However, the data forwarding module only selects the available connection to transmit data.

[0139] Step 6. The link management module determines whether the state of the host service S0 has changed. If yes, step 7 is performed. Otherwise, step 8 is performed.

[0140] Step 7. The link management module determines whether the state of the host service S0 changes from available to unavailable. The proxy publishing module calls the service directory interface of the open system to perform service deregistration of the host service S0. If the state of the host service S0 changes from unavailable to available, the attribute information M1 of the host service S0 is constructed according to the metadata M0 corresponding to the host service S0, in combination with the node information and service interface of the MATIP gateway. The proxy publishing module calls the SOA architecture service directory interface to perform service registration of the host service S0. At this time, the open system can complete service addressing according to the service name S0.

[0141] In this step 7, the SOA architecture service directory interface writes the attribute information M1 into the service directory.

[0142] Here, the attribute information M1 includes the service name, the service address (the IP of the MATIP gateway), the service port, the data protocol supported by the service, the maximum packet length, and the like.

[0143] Step 8. The link management module checks whether the exit signal is received. If yes, step 9 is performed. Otherwise, step 5 is performed.

[0144] Step 9. If the host service S0 has not completed service deregistration, the proxy publishing module calls the SOA architecture service directory interface to perform service deregistration of the host service S0.

[0145] In this step 9, the SOA architecture service directory interface removes the attribute information M1 from the service directory.

[0146] Step 10. The resources of the host service S0 are cleaned up, and the exit is performed.

[0147] In the above process, the link management module is a background task of the MATIP gateway, monitors the change of MATIP resource information, when the MATIP resource increases, starts a new MATIP connection, and joins a group corresponding to a host service; if the MATIP resource is deleted, the corresponding MATIP connection needs to be terminated, and the corresponding host service group is removed. The link management module provides the host service state query according to the state of the group link.

[0148] It should be noted that the configuration information changes may be updates of existing host services, and reissuing is equivalent to updating the existing host services.

[0149] If it is a change to an existing service, the monitoring of the release after the configuration change is implemented to update the existing service.

[0150] In order to realize reliable and stable data between host services and open services, in the multi-live target service scenario, the request message end needs to quickly obtain the list of available nodes on the opposite side when selecting a target service instance, and isolate the fault node in time. The availability of the foregoing host service is provided by the link management module, which updates in time according to the state of the maintained MATIP link, and provides the list of available MATIP links corresponding to a host service to the data forwarding module. In the scenario of host requesting open service, the host service request message needs to be forwarded through the service bus ESB in the SOA architecture, so the MATIP gateway needs to perform health check on the service bus ESB node, which is completed by the node alive detection module. The node alive detection module uses active node alive detection and passive health state update dependent on business request messages to realize the health state update of the service bus ESB node by the MATIP gateway. The implementation steps are as follows:

[0151] Step 1. Create a node health state shared memory for the node alive detection module and the data forwarding module.

[0152] Step 2. For each ESB node in the ESB node list, start a timing task to actively detect the service port of the ESB node, if successful, the health state value of the ESB node in the shared memory is +1, and the unhealth value is set to 0; if not successful, the unhealth state value of the node in the shared memory is +1, and the health value is set to 0; if the health value or the unhealth value reaches the set threshold, it means that the ESB node state is consistent after continuous multiple detections, and the state of the ESB node in the shared memory is set to available or unavailable according to the state.

[0153] Step 3. While actively probing, the health state value and unhealth state value are updated using the result of sending and receiving messages in the data forwarding module; if sending or receiving is successful, the health state value is incremented by 1, and the unhealth value is set to 0; otherwise, if it fails, the unhealth state value is incremented by 1, and the health value is set to 0. Step 3 can achieve fast update of the health state according to the forwarding result of the request message.

[0154] By using the active probing and passive checking mechanisms described above, the node probing module achieves efficient health checking between nodes.

[0155] In the implementation of the protocol adaptation module, it is considered that the UNISYS host only supports the MATIP protocol when interacting with external systems, and the carried data format is IATA format data, while the data of the open system under the SOA architecture is mostly in JSON or XML data format. Although the communication protocols of the open system are diversified, various protocols can be shielded through the service bus ESB. Therefore, in data conversion, the MATIP gateway needs to realize the conversion between the IATA format used by the host service and the JSON or XML-based data format used by the open service. In the adaptation of the communication protocol, the MATIP gateway acts as a MATIP client to connect the UNISYS host service, and also acts as a client of the ESB to connect the ESB node using the enterprise's private protocol. The UNISYS host service and the ESB in the SOA architecture do not need to add any adaptation, and there is no invasion to the existing host system and the open system.

[0156] After solving the service publishing of the UNISYS host service under the SOA architecture, combining the functions of the protocol conversion module and the node probing module, the data forwarding module realizes the business interconnection between the host service and the open service, and according to the difference of the request message initiator, it is divided into two scenarios: access from the open service under the SOA architecture to the host service and access from the host service to the open service under the SOA architecture.

[0157] Under the premise that the MATIP gateway completes the service publishing of the UNISYS host service in the service directory of the SOA architecture, the data interaction of the scenario in which the open service request message of the SOA architecture requests the host service is as shown in Figure 3 The overall implementation steps are as follows:

[0158] Step 1: The processing node of the open service with the name S1 sends an open service request message to the service bus ESB, and the open service request message carries the target host service name S2.

[0159] Here, the service name is a logical concept, and a service may have multiple deployments, for example, the service S1 may have processing nodes N1, N2, and N3, etc.

[0160] Step 2: The ESB acquires the IP and port information of the service according to the attribute information of the target host service name S2 found from the service directory.

[0161] In this scenario, the target host service with the name S2 is the host service, and the MATIP gateway is used to proxy the publication of the host service in this case. Therefore, when processing the request sent to the target host service S2, the ESB acquires the IP and port information of the MATIP gateway, and forwards the request message to the MATIP gateway.

[0162] Step 3: The MATIP gateway parses the header of the request message and acquires the target host service name S2 to be sent.

[0163] Here, the MATIP gateway first performs access control and flow control inspection, and after the inspection passes, calls the link management module interface according to the target host service name S2, acquires the list of currently available MATIP links corresponding to the target host service name S2 by using the correspondence between the host service names and the grouping MATIP link resources, selects a MATIP link according to the load balancing strategy, and completes the conversion of the received request message data into the data format of the target host service S2 by using the protocol conversion module, and sends the converted data through the selected MATIP link.

[0164] Step 4: The processing node of the UNISYS target host service S2 sends a response to the MATIP gateway after completing the processing.

[0165] Step 5: After receiving the response of the processing node of the target host service S2, the MATIP gateway converts the response into the data format of the internal protocol under the SOA architecture, and returns the response to the ESB through the original route.

[0166] Step 6: The ESB returns the response to the processing node of the open service S1, and the process ends.

[0167] The data interaction of the UNISYS host service request message in the open service scenario under the SOA architecture is shown in FIG. 6. Figure 4 The overall implementation steps are as follows:

[0168] Step 1: The MATIP gateway establishes and maintains the MATIP connection with the processing node of the host service S3.

[0169] Step 2: The processing node of the host service S3 initiates a host service request message to the processing node of the open service S4 through the MATIP link between the MATIP gateway. The host service request message carries the target open service name.

[0170] Step 3: After receiving the request of the host service S3, the MATIP gateway selects the available ESB node according to the service bus ESB node information in the cache and the node state information provided by the node alive component, and selects the ESB target node to be sent according to the load balancing strategy.

[0171] The ESB refers to the entire service bus, which is deployed in a cluster in the implementation and is composed of multiple ESB nodes. The service directory of the ESB stores the service name and the IP address information of the processing node providing the corresponding service.

[0172] Step 4: The protocol conversion module is used to complete the data format conversion of the received host service request message to the internal protocol under the SOA architecture, and the host service request message is sent to the target ESB node.

[0173] Step 5: The target ESB node in the SOA architecture sends the host service request message to the processing node of the open service S4.

[0174] Step 6: The ESB receives the host service request response message returned by the processing node of the open service S4, and forwards the response to the MATIP gateway.

[0175] Step 7: The MATIP gateway receives the host service request response message returned by the ESB node, the protocol conversion module completes the conversion of the open data to the IATA data format, returns the host service S3 processing node through the MATIP link, and the process ends.

[0176] The present case proposes a method and device for realizing the service publishing and governance of the civil aviation host service in the SOA architecture. By constructing the MATIP gateway, the service definition and publishing of the host service in the SOA architecture are agented, and the service governance mechanism in the service interaction process of the host service and the open service is realized. The MATIP gateway realizes the data format conversion and communication protocol adaptation between the UNISYS host service and the open service, and supports the business interaction between the host service and the open service. The newly added MATIP gateway is non-invasive to the UNISYS host system and the open system under the SOA architecture, and ensures the stability of the system.

[0177] Based on the above method, the device corresponding to the above method is also provided, which includes a configuration management module, a link management module and an agent publishing module.

[0178] The configuration management module is configured to detect and load the configuration information of the host service, and the configuration information includes grouping information of the MATIP link resource between the MATIP gateway and the host system.

[0179] The link management module is configured to define and save the correspondence between the host service name and the grouped MATIP link resource according to the grouping information of the grouped MATIP link resource, create metadata corresponding to the host service, and create MATIP connections in sequence according to the grouped MATIP link resource.

[0180] The agent publishing module is configured to construct attribute information of the host service according to the metadata corresponding to the host service and in combination with node information and a service interface of the MATIP gateway, and invoke the SOA architecture service directory interface based on the attribute information of the host service, so that the SOA architecture service directory interface writes the attribute information of the host service into the service directory, and completes service registration.

[0181] Further, the link management module is further configured to monitor changes in MATIP link resource information, start a new MATIP connection when the MATIP link resource information is added, add the new MATIP connection to the grouped MATIP link resource corresponding to a certain host service name, terminate the MATIP connection corresponding to the deleted MATIP link resource when the MATIP link resource information is deleted, and remove the MATIP link resource from the MATIP link group resource corresponding to the host service, and provide host service state query according to the state of the grouped MATIP link.

[0182] Further, the device further comprises an agent publishing module, which is further configured to query the link management module before invoking the SOA architecture service directory interface based on the attribute information of the host service, and query that the host service is available.

[0183] Further, the link management module is further configured to trigger the agent publishing module when it is queried that the host service is unavailable or a quit signal is received.

[0184] The agent publishing module is further configured to invoke the SOA architecture service directory interface based on the trigger of the link management module, so that the SOA architecture service directory interface removes the attribute information of the host service from the service directory, and completes service deregistration.

[0185] Further, the device further comprises:

[0186] The node alive detection module is configured to determine the state of the ESB node based on the detection result of the IP address and the service port of the ESB node, and / or determine the state of the ESB node based on the result of sending and receiving the message in the service request message, wherein the state of the ESB node is available or unavailable.

[0187] Further, the device further comprises:

[0188] The data forwarding module is configured to receive the open service request message, select a MATIP link from the obtained MATIP link list, and forward the open service request message to a target host service processing node by using the selected MATIP link; and receive an open service response message and send the open service response message to the ESB.

[0189] The link management module is configured to obtain a MATIP link list corresponding to a target host service name carried in the open service request message by using the correspondence between the saved host service name and the grouped MATIP link resource.

[0190] Further, the data forwarding module is specifically configured to select a MATIP link from the obtained MATIP link list according to a load balancing strategy and a MATIP link state.

[0191] Further, the apparatus further comprises:

[0192] The data forwarding module is configured to receive a host service request message, determine a target ESB node based on a target open service name and cached ESB node information, send the host service request message to the target ESB node, and receive and forward a host service response message from the ESB node to a host service processing node.

[0193] Based on the same inventive concept as disclosed above, the disclosure also provides an electronic device. The electronic device of the embodiments of the disclosure comprises at least one processor and at least one memory electrically connected, wherein the memory is electrically connected with the processor, and the memory stores instructions executable by the at least one processor. The instructions are executed by the at least one processor to enable the at least one processor to perform the method as described above.

[0194] It should be noted that the electrical connection between the above-mentioned various units does not necessarily mean the connection between the lines, and the indirect connection mode can also be applicable to the embodiments of the disclosure as long as the purpose of the disclosure is achieved.

[0195] Based on the same inventive concept, the disclosure also provides a computer storage medium, wherein the computer storage medium stores a computer program, and the computer program is executed by a processor to implement the steps of the above method.

[0196] Although the disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that the technical solutions recorded in the foregoing embodiments can be modified, or some technical features can be replaced by equivalent features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the disclosure.

Claims

1. A service processing system, characterized in that: The system includes: a UNISYS host system, a MATIP gateway, an ESB in the SOA architecture, and an open system; wherein the MATIP gateway bridges the UNISYS host system and the ESB in the SOA architecture; UNISYS host system, used to provide host services; The MATIP gateway is used to detect and load the configuration information of the host service. According to the grouping information of the MATIP link resources in the configuration information, it defines and saves the correspondence between the host service name and the grouped MATIP link resources, and creates metadata corresponding to the host service. It sequentially creates MATIP connections according to the grouped MATIP link resources. Based on the metadata corresponding to the host service, combined with the node information and service interface of the MATIP gateway, it constructs the attribute information of the host service. Based on the attribute information of the host service, it calls the SOA architecture service directory interface through the ESB to complete the service registration. ESB, used to connect open systems, provide service catalogs, perform protocol conversion, and message routing; Open system, used to provide open services.

2. The service processing system according to claim 1, wherein: The MATIP gateway is further configured to monitor changes in MATIP link resource information; upon addition, initiate a new MATIP connection and add the new MATIP connection to the grouped MATIP link resources corresponding to a host service name; upon deletion, terminate the MATIP connection corresponding to the deleted MATIP link resource and remove it from the MATIP link grouped resources of the corresponding host service; and provide host service status query based on the status of the grouped MATIP link.

3. The service processing system according to claim 2, wherein: The MATIP gateway is specifically used to complete service registration by calling the SOA architecture service directory interface through ESB based on the attribute information of the host service when it is queried that the host service is available.

4. The service processing system according to any one of claims 1 to 3, characterized in that: The MATIP gateway is also used to call the SOA architecture service directory interface through ESB to complete service deregistration when it is found that the host service is unavailable or an exit signal is received.

5. The service processing system according to any one of claims 1 to 3, characterized in that: The MATIP gateway is further configured to determine the status of the ESB node based on the detection results of the IP address and service port of the ESB node; and / or determine the status of the ESB node based on the results of sending and receiving messages in the service request message, wherein the status of the ESB node is available or unavailable.

6. The service processing system according to claim 1, wherein: The host system includes a host service processing node; the open system includes an open service processing node; The open service processing node is used to send the open service request message carrying the target host service name to the ESB; and receiving an open service response message; The ESB is used to search the service directory for a MATIP gateway address corresponding to a service name that matches the service name of the target host, and send an open service request message using the found MATIP gateway address; and receiving and forwarding the open service response message to the open service processing node; The MATIP gateway is further configured to receive an open service request message, obtain a MATIP link list corresponding to a target host service name carried in the open service request message using a stored correspondence between host service names and grouped MATIP link resources, select a MATIP link from the obtained MATIP link list, and forward the open service request message to a target host service processing node using the selected MATIP link; and receiving an open service response message, and sending the open service response message to the ESB; The host service processing node is configured to receive an open service request message sent by the MATIP gateway, process the open service request message, obtain an open service response message, and send the open service response message to the MATIP gateway.

7. The service processing system according to claim 6, wherein: The MATIP gateway is specifically configured to select a MATIP link from the acquired MATIP link list according to a load balancing strategy and a MATIP link status.

8. The service processing system according to claim 1, wherein: The host system includes a host service processing node, the open system includes an open service processing node, and the ESB is composed of multiple ESB nodes; The host service processing node is used to send the host service request message carrying the target open service name to the MATIP gateway; and receiving a host service response message; The MATIP gateway is further configured to receive a host service request message, determine a target ESB node based on the target open service name and cached ESB node information, and send the host service request message to the target ESB node; and receiving and forwarding the host service response message to the host service processing node; The ESB node is configured to receive a host service request message, search a service directory for a service name that matches a target open service name, determine an open service processing node that provides the target open service, and send the host service request message to the determined open service processing node; And receive and forward the host service response message to the MATIP gateway; The open service processing node is used to receive a host service request message sent by the ESB node, process the host service request message, obtain a host service response message, and send the host service response message to the ESB node.

9. The service processing system according to any one of claims 6 to 8, characterized in that: The MATIP gateway is also used to perform protocol and data format adaptation on request and response messages before forwarding them. For host service request messages and open service response messages, the protocol and data format adaptation is performed using the enterprise private protocol based on TCP within the ESB; and for host service response messages and open service request messages, the protocol and data format adaptation is performed using MATIP.

10. A service processing method, characterized in that: The method comprises: Detecting and loading configuration information of the host service, the configuration information includes: grouping information of MATIP link resources between the MATIP gateway and the host system; According to the grouping information of the grouped MATIP link resources, define and save the correspondence between the host service name and the grouped MATIP link resources, and create metadata corresponding to the host service; Create MATIP connections in sequence according to the grouped MATIP link resources; According to the metadata corresponding to the host service, combined with the node information and service interface of the MATIP gateway, the attribute information of the host service is constructed; Based on the attribute information of the host service, the SOA architecture service directory interface is called through the ESB so that the SOA architecture service directory interface writes the attribute information of the host service into the service directory to complete the service registration.

11. The method according to claim 10, characterized in that The method further comprises: Monitor changes in MATIP link resource information; When adding, a new MATIP connection is started and added to the grouped MATIP link resource corresponding to a host service name; when deleting, the MATIP connection corresponding to the deleted MATIP link resource is terminated and removed from the MATIP link group resource of the corresponding host service; Provides host service status query based on the status of the packet MATIP link.

12. The method according to claim 11, characterized in that Before calling the SOA architecture service catalog interface through the ESB based on the attribute information of the host service, the method further includes: Verify that the host service is available.

13. The method according to any one of claims 10 to 12, characterized in that: When it is found that the host service is unavailable or an exit signal is received, the SOA architecture service directory interface is called through ESB so that the SOA architecture service directory interface can remove the attribute information of the host service from the service directory and complete the service deregistration.

14. The method according to any one of claims 10 to 12, characterized in that: The method further comprises: The state of the ESB node is determined based on the detection results of the IP address and service port of the ESB node; and / or the state of the ESB node is determined based on the results of sending and receiving messages in the service request message, wherein the state of the ESB node is available or unavailable.

15. The method according to claim 10, characterized in that The method further comprises: Receive open service request message; Using the saved correspondence between host service names and group MATIP link resources, obtain the MATIP link list corresponding to the target host service name carried in the open service request message; Select a MATIP link from the obtained MATIP link list, and forward the open service request message to the target host service processing node using the selected MATIP link; Receive the open service response message and send the open service response message to the ESB.

16. The method according to claim 15, characterized in that Select a MATIP link from the obtained MATIP link list, including: Select a MATIP link from the obtained MATIP link list based on the load balancing policy and MATIP link status.

17. The method according to claim 10, wherein: The method further comprises: Receive a host service request message carrying the target open service name; Determine the target ESB node based on the target open service name and cached ESB node information; Send the host service request message to the target ESB node; Receive and forward host service response messages from the ESB node to the host service processing node.

18. The method according to any one of claims 15 to 17, characterized in that: The method further comprises: Before forwarding the request and response messages, the protocol and data format are adapted. For the host service request message and the open service response message, the protocol and data format are adapted using the enterprise private protocol based on TCP within the ESB; for the host service response message and the open service request message, the protocol and data format are adapted using MATIP.

19. A service processing device, characterized in that: The device includes: a configuration management module, a link management module and an agent publishing module; wherein: A configuration management module is used to detect and load configuration information of the host service, wherein the configuration information includes: grouping information of MATIP link resources between the MATIP gateway and the host system; The link management module is used to define and save the correspondence between the host service name and the grouped MATIP link resources according to the grouping information of the grouped MATIP link resources, create metadata corresponding to the host service; and sequentially create MATIP connections according to the grouped MATIP link resources; The proxy publishing module is used to construct the attribute information of the host service according to the metadata corresponding to the host service, combined with the node information and service interface of the MATIP gateway; based on the attribute information of the host service, the SOA architecture service directory interface is called through the ESB so that the SOA architecture service directory interface writes the attribute information of the host service into the service directory to complete the service registration.

20. The device according to claim 19, characterized in that The link management module is further configured to monitor changes in MATIP link resource information; upon addition, initiate a new MATIP connection and add the new MATIP connection to the grouped MATIP link resources corresponding to a host service name; upon deletion, terminate the MATIP connection corresponding to the deleted MATIP link resource and remove it from the MATIP link grouping resources of the corresponding host service; and provide host service status query based on the status of the grouped MATIP link.

21. The device according to claim 20, characterized in that The device further comprises: an agent publishing module, which is further used to query the link management module based on the attribute information of the host service before calling the SOA architecture service directory interface through the ESB to query that the host service is available.

22. The device according to any one of claims 19 to 21, characterized in that: The link management module is further configured to trigger the proxy publishing module when it finds that the host service is unavailable or receives an exit signal; The proxy publishing module is also used to call the SOA architecture service directory interface through ESB under the triggering of the link management module, so that the SOA architecture service directory interface can remove the attribute information of the host service from the service directory and complete the service deregistration.

23. The device according to any one of claims 19 to 21, characterized in that The device further comprises: The node activity detection module is used to determine the status of the ESB node based on the detection results of the IP address and service port of the ESB node; and / or determine the status of the ESB node based on the results of sending and receiving messages in the service request message, where the status of the ESB node is available or unavailable.

24. The device according to claim 19, characterized in that The device further comprises: The data forwarding module is used to receive the open service request message, select a MATIP link from the obtained MATIP link list, and forward the open service request message to the target host service processing node using the selected MATIP link; receive the open service response message, and send the open service response message to the ESB; The link management module is used to obtain the MATIP link list corresponding to the target host service name carried in the open service request message by using the stored correspondence between the host service name and the group MATIP link resources.

25. The device according to claim 24, characterized in that The data forwarding module is specifically configured to select a MATIP link from the acquired MATIP link list according to the load balancing policy and the MATIP link status.

26. The device according to claim 19, characterized in that The device further comprises: The data forwarding module is also used to receive the host service request message, determine the target ESB node based on the target open service name and cached ESB node information; send the host service request message to the target ESB node; and receive and forward the host service response message from the ESB node to the host service processing node.

27. The device according to any one of claims 24 to 26, characterized in that: The data forwarding module is also used to adapt the protocol and data format before forwarding the request message and the response message. For the host service request message and the open service response message, the protocol and data format are adapted using the enterprise private protocol based on TCP within the ESB; for the host service response message and the open service request message, the protocol and data format are adapted using MATIP.

28. An electronic device, characterized in that: comprising at least one processor and at least one storage medium electrically connected; the storage medium being connected to the processor bus; wherein, The storage medium stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the service processing method according to any one of claims 10 to 18.

29. A computer storage medium, characterized in that The storage medium stores instructions that can be executed by at least one processor; the instructions are executed by the at least one processor so that the at least one processor can execute the service processing method according to any one of claims 10 to 18.

Images