Service processing system, method and device, electronic equipment and storage medium

Abstract

The invention relates to the technical field of computers, and provides a service processing system, method and device, electronic equipment and a storage medium, the system comprises a UNISY host system, an MATIP gateway, an ESB in an SOA architecture and an open system; the gateway is in bridge connection with the host system and the ESB, detects and loads configuration information of a host service, defines and stores a corresponding relation between a host service name and packet link resources according to packet information of the link resources, and creates metadata corresponding to the host service; mATIP connection is created according to the grouped link resources; according to the metadata corresponding to the host service, combining the node information and the service interface of the gateway to construct attribute information of the host service; and calling an SOA architecture service directory interface through the ESB to complete service registration. A gateway is constructed, and corresponding services in a host are abstractly mapped by utilizing a packet link between the gateway and a host system, so that service definition and release of host services in an open system are agented.

Description

Technical Field

[0001] The present disclosure belongs to the field of computer technology, and in particular, relates to a service processing system, method, device, electronic device and storage medium. Background Art

[0002] In the context of globalization, aviation logistics, as an important part of international trade, has become an important support for national economic development. Early civil aviation information systems mostly used UNISYS mainframe systems, which used private protocols internally and centrally processed all business needs. When interacting with external airlines and GDS (Global distribution system), the host system needs to follow the standard MATIP (Mapping of Airline Reservation, Ticketing and Messaging Traffic over IP, mapping of airline reservation, ticketing and message data on IP networks, i.e., aviation traffic service IP group) protocol for data interaction. The MATIP protocol is an end-to-end TCP network transmission encapsulation aviation-specific protocol data packet, which realizes the establishment of a routing-independent mapping standard between the transport layer and aviation applications.

[0003] With the rapid increase in civil aviation business models and processing volume, the model of centralized processing of business by large-scale mainframe systems has become a bottleneck restricting the development of civil aviation business informatization. More and more businesses are beginning to shift to open and distributed systems. During the migration process, facing the numerous interaction requirements between open systems and host systems, how to solve the service processing of host services in the open system architecture, such as service definition and release, fault isolation, protocol adaptation and monitoring management, etc., and realize reliable and stable data interaction between host services and open services has become an important issue faced in the process of business migration.

[0004] SOA (Service-Oriented Architecture) divides daily business applications into separate 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 applications and their operating platforms, thereby improving the flexibility of business processes, accelerating development speed and reducing development costs.

[0005] Currently, there is no service processing that can realize various host services in the open SOA architecture. In order to support business interaction between host services and open services, it is necessary to realize service processing of various host services in the open SOA architecture. Therefore, it is necessary to provide a service processing system, method, device, electronic device and storage medium. Summary of the invention

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

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

[0008] UNISYS host system, used to provide host services;

[0009] The MATIP gateway is used to detect and load the configuration information of the host service, define and save the correspondence between the host service name and the grouped MATIP link resources according to the grouping information of the MATIP link resources in the configuration information, and create metadata corresponding to the host service; create MATIP connections in sequence according to the grouped MATIP link resources; 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, call the SOA architecture service directory interface through ESB to complete the service registration;

[0010] ESB, used to connect open systems, provide service catalogs, perform protocol conversion, and message routing;

[0011] Open system, used to provide open services.

[0012] Furthermore, the MATIP gateway is also used to monitor changes in MATIP link resource information; when adding, start a new MATIP connection and add the new MATIP connection to the grouped MATIP link resources corresponding to a host service name; when deleting, terminate the MATIP connection corresponding to the deleted MATIP link resource and remove it from the MATIP link group resources of the corresponding host service; provide host service status query according to the status of the grouped MATIP link.

[0013] Furthermore, 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.

[0014] Furthermore, the MATIP gateway is also used to complete service deregistration by calling the SOA architecture service directory interface through ESB when it is found that the host service is unavailable or an exit signal is received.

[0015] Furthermore, the MATIP gateway is also 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, wherein the status of the ESB node is available or unavailable.

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

[0017] The open service processing node is used 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 used to search the MATIP gateway address corresponding to the service name matching the target host service name in the service directory, send the open service request message 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 used 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 by using a stored correspondence between a host service name and a grouped MATIP link resource, 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;

[0020] The host service processing node is used 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 an open service response message to the MATIP gateway.

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

[0022] 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;

[0023] The host service processing node is used 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 used 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;

[0025] The ESB node is used to receive a host service request message, search for a service name that matches a target open service name from a service directory, and then 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;

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

[0027] Furthermore, the MATIP gateway is also used to perform protocol and data format adaptation before forwarding the request message and the response message, wherein the protocol and data format adaptation is performed for the host service request message and the open service response message using the enterprise private protocol based on TCP within the ESB; and the protocol and data format adaptation is performed for the host service response message and the open service request message using MATIP.

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

[0029] 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;

[0030] 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;

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

[0032] 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;

[0033] 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.

[0034] Furthermore, the method further comprises:

[0035] Monitor changes in MATIP link resource information;

[0036] When adding, a new MATIP connection is started and added to the grouped MATIP link resource corresponding to a certain host service name; when deleting, the MATIP connection corresponding to the deleted MATIP link resource is terminated and removed from the MATIP link grouping resource of the corresponding host service;

[0037] Provide host service status query based on the status of the packet MATIP link.

[0038] Furthermore, the method further comprises:

[0039] Based on the attribute information of the host service, before calling the SOA architecture service catalog interface through the ESB, the method further includes:

[0040] Verify that the host service is available.

[0041] Furthermore, it is characterized in that

[0042] 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 the ESB so that the SOA architecture service directory interface removes the attribute information of the host service from the service directory and completes the service deregistration.

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

[0044] 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.

[0045] Furthermore, the method further comprises:

[0046] Receive an open service request message;

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

[0048] Select a MATIP link from the acquired MATIP link list, and use the selected MATIP link to forward the open service request message to the target host service processing node;

[0049] Receive the open service response message, and send the open service response message to the ESB.

[0050] Further, a MATIP link is selected from the obtained MATIP link list, specifically including:

[0051] Select a MATIP link from the obtained MATIP link list according to the load balancing policy and MATIP link status.

[0052] Furthermore, the method further comprises:

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

[0054] Determine the target ESB node based on the target open service name and cached ESB node information;

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

[0056] Receive and forward host service response messages from ESB nodes to host service processing nodes.

[0057] Furthermore, the method further comprises:

[0058] Before forwarding the request message and response message, 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.

[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 an agent publishing module; wherein:

[0060] A configuration management module, used to detect and load configuration information of a host service, wherein the configuration information includes: grouping information of MATIP link resources between a MATIP gateway and a host system;

[0061] 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 create MATIP connections in sequence according to the grouped MATIP link resources;

[0062] 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 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.

[0063] Furthermore, the link management module is also used to monitor changes in MATIP link resource information; when adding, start a new MATIP connection and add the new MATIP connection to the grouped MATIP link resources corresponding to a host service name; when deleting, terminate the MATIP connection corresponding to the deleted MATIP link resource and remove it from the MATIP link group resources of the corresponding host service; provide host service status query according to the status of the grouped MATIP link.

[0064] Furthermore, the device also includes: an agent publishing module, which is also 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 ESB to query whether the host service is available.

[0065] Furthermore, the link management module is also used to trigger the proxy publishing module when it is found that the host service is unavailable or an exit signal is received;

[0066] 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 removes the attribute information of the host service from the service directory and completes the service deregistration.

[0067] Furthermore, the device also includes:

[0068] The node 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.

[0069] Furthermore, the device also includes:

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

[0071] 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.

[0072] Furthermore, the data forwarding module is specifically configured to select a MATIP link from the acquired MATIP link list according to the load balancing strategy and the MATIP link status.

[0073] Furthermore, the device also includes:

[0074] 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.

[0075] Furthermore, the data forwarding module is also used to perform protocol and data format adaptation 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 adaptation is performed 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 adaptation is performed 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 bus; wherein,

[0077] 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 so that the at least one processor can execute the above-mentioned service processing method.

[0078] In a fifth aspect, a computer storage medium stores instructions executable 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 above-mentioned service processing method.

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

[0080] 1. By building a MATIP gateway, the grouped MATIP link between the MATIP gateway and the host system is used to abstractly map the corresponding services in the host, thereby acting as the agent for the service definition and release of the host service in the open system;

[0081] 2. Through the management and maintenance of packet MATIP links, the host service can be upgraded and maintained in an open system, including traffic protection, service routing, load balancing, isolation and recovery.

[0082] 3. MATIP gateway realizes the conversion between the format used by the host service and the data format used by the open service; in terms of communication protocol adaptation, MATIP gateway acts as a MATIP client to connect to the UNISYS host service, and as an ESB client, it uses the enterprise's internal private protocol to connect to the ESB node. The host system and the ESB in the SOA architecture do not need to add any adaptation, and are non-invasive to the existing host system and open system.

[0083] Other features and advantages of the present disclosure will be described in the following description, and partly become apparent from the description, or be understood by implementing the present disclosure. The purpose and other advantages of the present disclosure can be realized and obtained by the structures pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0084] In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[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 schematic diagram of a service publishing and updating process flow chart of a host service under a SOA architecture according to an embodiment of the present disclosure is shown;

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

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

[0089] In order to make the purpose, technical solution and advantages of the embodiments of the present disclosure clearer, the technical solution in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the drawings in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, not all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

[0090] In the face of the diversification of business system technologies and the difficulty of transforming legacy systems, ESB (Enterprise Service Bus) implementation plans are usually adopted to reduce the complexity and coupling of interactions between systems. In a narrow sense, ESB is a pipeline used to connect various service nodes. In order to integrate services of different systems and protocols, it focuses on message conversion, protocol adaptation and routing, realizes the interconnection of different services, and assumes the role of interactive services. In a broad sense, ESB expands its scope to management services and process services, providing functions such as service catalog management, runtime monitoring and service aggregation.

[0091] In the process of opening up civil aviation business, open systems are usually deployed using SOA architecture, and ESB is used to integrate open services of various protocols. In large civil aviation mainframe systems, each host service published to the outside needs to have a set of MATIP resources, which are used to establish connections with external systems and exchange data. The gateway is an important bridge connecting the local network and the external network, which can achieve smooth communication between the two networks. Therefore, the combination of the two can publish the host service in the service directory in the SOA architecture through the gateway via ESB. From the perspective of open systems, a set of MATIP links corresponds to a host service, so the governance of a host service under the SOA architecture can be converted to 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 realizing host services in an open system, and service processing mainly includes service publishing and governance. By constructing a MATIP gateway, the grouped MATIP link between the MATIP gateway and the host system is used to abstractly map the corresponding services in the host, thereby acting as an agent for the service definition and publishing of the host service in the open system; by managing and maintaining the grouped MATIP link, the host service in the open system can realize the upgrade maintenance, traffic protection, service routing, load balancing, isolation and recovery and other service governance functions.

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

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

[0095] MATIP gateway is used to publish services on behalf of host services (business processing units in the UNISYS host system) to the SOA architecture, providing support for the interaction between the host system and the open system, and realizing business interconnection between the host system and the open system;

[0096] ESB is used to provide a service catalog, perform protocol conversion and message routing.

[0097] The MATIP gateway includes a configuration management module, an agent publishing module, a link management module, a node detection module, a protocol adaptation module and a data forwarding module, among which:

[0098] The configuration management module is used to group MATIP resources, maintain the mapping relationship with the host service, store the routing, flow control, data conversion and other rules between the host service and the open service, and realize the dynamic management of configuration items.

[0099] The proxy publishing module is used to realize the publishing and updating of the service catalog of the host service in the SOA architecture to support the addressing of the host service by the service bus ESB under the SOA architecture.

[0100] The link management module is used to create and maintain the MATIP link with the host service, realize the isolation and recovery of the host node, and provide the host service status query to the proxy publishing module and the data forwarding module according to the status of the group MATIP link. When there is an available MATIP link in the group MATIP link, the status of the host service status is available, and when there is no available MATIP link in the group MATIP link, the status of the host service status is unavailable.

[0101] The node detection module is used to detect the activity of the SOA architecture service bus ESB node, implement the isolation and recovery mechanism of the ESB node, and provide support for routing decisions in the data forwarding process.

[0102] The protocol adapter module is used to implement bidirectional conversion between MATIP used in the host system and the enterprise private protocol based on TCP within the ESB.

[0103] The data forwarding module is used to receive SOA request messages from the ESB service bus, forward them to the target host service, select the target node according to the routing, load balancing and traffic control rules, and complete the message conversion using the functions provided by the protocol adapter module.

[0104] In the above module:

[0105] As one of the background tasks of the MATIP gateway, the configuration management module provides the management function of gateway configuration items. By managing the MATIP resources between the gateway and the host service, it provides the basic attribute information of the service to be released to the proxy publishing module and provides the metadata for creating the MATIP link to the link management module. When the service governance-related rules change, the gateway cache is updated in time to provide a basic guarantee for the processing of other modules.

[0106] The proxy publishing module is designed to solve the service publishing of host services in SOA architecture deployment. The proxy publishing module obtains the group MATIP link corresponding to a host service from the configuration management module, obtains the service status corresponding to the group MATIP link from the link management module, and initiates service information update to the SOA service directory.

[0107] The node detection module can implement active and passive health checks. In the active detection mechanism, the ESB node status is updated by periodically detecting the ESB node IP and service port. For example, if the ESB node status is successful or unhealthy for three consecutive times, it is considered healthy or unhealthy. In the passive detection mechanism, with the help of the connection with the ESB node, when sending or receiving data successfully or unsuccessfully, the health / unhealthy status count value of the ESB node is updated. If the count value reaches a certain threshold, the ESB node status is considered healthy or unhealthy.

[0108] The MATIP gateway bridges the host service and the ESB under the SOA architecture. The protocol adapter module implements the adaptation and conversion of different communication protocols and data formats, so that existing deployments and services do not need to add new adapter components, and are non-invasive to the existing UNISYS host system and open system. In the process of the SOA service request message UNISYS host service, the SOA service sends the request message to the service bus ESB. Because the MATIP gateway uses the node information of the MATIP gateway as the node information of the microservice instance when the proxy host service publishes the 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 status and load balancing decision, and uses the protocol adapter module function to complete the message conversion and forward the data.

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

[0110] UNISYS host system, used to provide host services;

[0111] The MATIP gateway is used to detect and load the configuration information of the host service, define and save the correspondence between the host service name and the grouped MATIP link resources according to the grouping information of the MATIP link resources in the configuration information, and create metadata corresponding to the host service; create MATIP connections in sequence according to the grouped MATIP link resources; 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, call the SOA architecture service directory interface through ESB to complete the service registration;

[0112] ESB, used to connect open systems, provide service catalogs, perform protocol conversion, and message routing;

[0113] Open system, used to provide open services.

[0114] The above system solution realizes the service publishing of the host service in the SOA architecture.

[0115] Furthermore, the MATIP gateway is also used to monitor changes in MATIP link resource information; when adding, start a new MATIP connection and add the new MATIP connection to the grouped MATIP link resources corresponding to a host service name; when deleting, terminate the MATIP connection corresponding to the deleted MATIP link resource and remove it from the MATIP link group resources of the corresponding host service; provide host service status query according to the status of the grouped MATIP link.

[0116] Furthermore, 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.

[0117] Furthermore, the MATIP gateway is also used to complete service deregistration by calling the SOA architecture service directory interface through ESB when it is found that the host service is unavailable or an exit signal is received.

[0118] Furthermore, the MATIP gateway is also 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, wherein the status 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 used 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 used to search the MATIP gateway address corresponding to the service name matching the target host service name in the service directory, send the open service request message using the found MATIP gateway address; and receive and forward the open service response message to the open service processing node;

[0122] The MATIP gateway is further used 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 by using a stored correspondence between a host service name and a grouped MATIP link resource, 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;

[0123] The host service processing node is used 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 an 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 the load balancing strategy and the 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 used 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 used 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 used to receive a host service request message, search for a service name that matches a target open service name from a service directory, and then 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 used to receive a host service request message sent by an ESB node, process the host service request message, obtain a host service response message, and send a host service response message to the ESB node.

[0130] The above embodiments describe the functions of the service processing system in the present disclosure. The following describes the service processing solution of the present invention through specific embodiments.

[0131] Given that the host system follows the standard MATIP protocol when interacting with external systems, each host service uses one or more MATIP links to perform concurrent processing of business request messages. Therefore, in the implementation of the MATIP gateway, the packet MATIP link between the gateway and the host is used to abstractly map the corresponding services in the host, and the service definition of the host service under the open architecture is performed. The service mapping is maintained and managed through the configuration management module, and the proxy module is used to complete the service release of the host service under the open SOA architecture. During the service operation process, the link status information provided by the link management module is used to implement the service status update of the host service in the open SOA architecture.

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

[0133] Step 1. When the configuration management module detects that the configuration information has changed, it loads the configuration information.

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

[0135] Step 2. The configuration management module defines the correspondence between the newly added host service S0 and the MATIP resource R0 according to the grouping information of the MATIP resource, and creates 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 into 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 in sequence according to the MATIP resource R0 of the host service S0. If R0 is multiple MATIP resources, multiple MATIP connections are created, and then the MATIP connection maintenance state is entered.

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

[0139] Step 6. The link management module determines that if the host service S0 status changes, execute step 7, otherwise execute step 8.

[0140] Step 7. The link management module determines that if the status of the host service S0 changes from available to unavailable, the proxy publishing module calls the service directory interface of the open system to execute the service cancellation of the host service S0; if the status of the host service S0 changes from unavailable to available, it is necessary to construct the attribute information M1 of the host service S0 based on the metadata M0 corresponding to the host service S0 and the node information and service interface of the MATIP gateway, and the proxy publishing module calls the SOA architecture service directory interface to execute the service registration of the host service S0. At this time, the open system can complete the 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: service name, service address (IP of MATIP gateway), service port, data protocol supported by the service, maximum message length, etc.

[0143] Step 8. The link management module checks whether an exit signal is received. If an exit signal is received, execute step 9; otherwise, jump to step 5.

[0144] Step 9. If the host service S0 has not completed the service deregistration, the proxy publishing module calls the SOA architecture service directory interface to execute the 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. Clean up the resources of host service S0 and exit.

[0147] In the above process, the link management module, as a background task of the MATIP gateway, monitors the changes in MATIP resource information. When MATIP resources are increased, a new MATIP connection is started and added to the group corresponding to a host service. If the MATIP resources are deleted, the corresponding MATIP connection needs to be terminated and removed from the corresponding host service group. The link management module provides host service status query based on the status of the group link.

[0148] It should be noted that a change in configuration information may be an update to an existing host service, and re-releasing it is equivalent to updating the existing host service.

[0149] If the change is to an existing service, the release after monitoring the configuration change is implemented by updating the existing service.

[0150] In order to achieve reliable and stable data between the host service and the open service, in the scenario where the target service is multi-active, the request message end needs to be able to quickly obtain the list of available nodes on the other end when selecting the target service instance, and isolate the faulty node in time. The availability of the aforementioned host service is provided by the link management module. The link management module is updated in time according to the status of the maintained MATIP link, and provides the data forwarding module with a list of available MATIP links corresponding to a certain host service. In the scenario where the host requests an open service, the host service request message needs to be forwarded through the service bus ESB in the SOA architecture. Therefore, the MATIP gateway needs to perform a health check on the service bus ESB node. This function is completed by the node liveness detection module. The node liveness detection module uses the node active liveness detection and the passive health status update attached to the business request message to implement the MATIP gateway to update the health status of the service bus ESB node. The implementation steps are detailed as follows:

[0151] Step 1. Create a node health status shared memory for use by the node detection module and the data forwarding module.

[0152] Step 2. For each ESB node in the ESB node list, start a scheduled task to actively detect the service port of the ESB node. If successful, the health status value of the ESB node in the shared memory is increased by 1, and the unhealth value is set to 0; if unsuccessful, the unhealth status value of the node in the shared memory is increased by 1, and the health value is set to 0; if the health value or unhealth value reaches the set threshold, it indicates that the ESB node status is consistent after multiple consecutive detections, and the status of the ESB node in the shared memory is set to available or unavailable according to the status.

[0153] Step 3. While actively detecting liveness, the health status value and unhealth status value are updated using the results of sending and receiving messages in the data forwarding module; if sending or receiving is successful, the health status value is +1 and the unhealth value is set to 0; otherwise, if it fails, the unhealth status value is +1 and the health value is set to 0. This step 3 can achieve a fast update of the health status according to the forwarding result of the request message.

[0154] By using the above active detection and passive inspection mechanisms, the node detection module realizes efficient health checks 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 data format is IATA format data, while the open system data under the SOA architecture is mostly based on JSON or XML data format. Although the communication protocols of the open system are diverse, various different protocols can be shielded through the service bus ESB. Therefore, in terms of data conversion, the MATIP gateway needs to implement 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 terms of communication protocol adaptation, the MATIP gateway acts as a MATIP client to connect to the UNISYS host service, and as a client of the ESB, it uses the enterprise's internal private protocol to connect to the ESB node. The UNISYS host service and the ESB in the SOA architecture do not need to add any adaptation, and are non-invasive to the existing host system and open system.

[0156] After solving the service release of UNISYS host service under the SOA architecture, the data forwarding module combines the functions of the protocol conversion module and the node detection module to realize the business interconnection between the host service and the open service. According to the different initiators of the request message, it is divided into two scenarios: access from open services under the SOA architecture to host services and access from host services to open services under the SOA architecture.

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

[0158] Step 1: The processing node of the open service named 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] The service name here is a logical concept. A service may have multiple deployments. For example, service S1 may have processing nodes N1, N2, and N3, and so on.

[0160] Step 2: ESB obtains the IP and port information of the service based on the attribute information of the target host service name S2 found in the service directory.

[0161] In this scenario, the target host service named S2 is the host service. This case uses the MATIP gateway to proxy the release of the host service. Therefore, when processing the request sent to the target host service S2, the IP and port information of the service obtained by ESB is the MATIP gateway information, and ESB forwards the request message to the MATIP gateway.

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

[0163] Here, the MATIP gateway first performs access control and flow control inspections. After the inspection is passed, the link management module interface is called according to the target host service name S2, and the corresponding relationship between the saved host service name and the grouped MATIP link resources is used to obtain the currently available MATIP link list corresponding to the target host service name S2, and a MATIP link is selected according to the load balancing strategy. The protocol conversion module is used to complete the conversion of the received request message data to the target host service S2 data format, and the converted data is sent through the selected MATIP link.

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

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

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

[0167] UNISYS host service request message requests data interaction in open service scenarios under SOA architecture. Figure 4 As shown, the overall implementation steps are detailed as follows:

[0168] Step 1: The MATIP gateway establishes and maintains a 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 host service S3 and the MATIP gateway. The host service request message carries the target open service name;

[0170] Step 3: After receiving the request from the host service S3, the MATIP gateway selects the currently available ESB node based on the service bus ESB node information in the cache and the node status information provided by the node detection component, and selects the ESB target node to be sent based on the load balancing strategy.

[0171] ESB refers to the entire service bus, which is deployed in a clustered manner and consists of multiple ESB nodes. The service directory of ESB stores the service name and the IP address information of the processing node that provides the corresponding service.

[0172] Step 4: Use the protocol conversion module to complete the data format conversion of the received host service request message to the internal protocol under the SOA architecture, and send the host service request message 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: ESB receives the host service request response message returned by the processing node of 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, and the protocol conversion module completes the conversion of the open data to the IATA data format, and returns it to the processing node of the host service S3 through the MATIP link, and the process ends.

[0176] This case proposes a method and device for realizing service publishing and governance of civil aviation host services in SOA architecture. By constructing a MATIP gateway, the service definition and publishing of the proxy host service in the SOA architecture are realized, and the service governance mechanism in the interaction process between 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, ensuring the stability of the system.

[0177] Based on the above method, the embodiment of the present disclosure further provides a device corresponding to the above method, including: a configuration management module, a link management module and an agent publishing module; wherein:

[0178] A configuration management module, used to detect and load configuration information of a host service, wherein the configuration information includes: grouping information of MATIP link resources between a MATIP gateway and a host system;

[0179] 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 create MATIP connections in sequence according to the grouped MATIP link resources;

[0180] 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 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.

[0181] Furthermore, the link management module is also used to monitor changes in MATIP link resource information; when adding, start a new MATIP connection and add the new MATIP connection to the grouped MATIP link resources corresponding to a host service name; when deleting, terminate the MATIP connection corresponding to the deleted MATIP link resource and remove it from the MATIP link group resources of the corresponding host service; provide host service status query according to the status of the grouped MATIP link.

[0182] Furthermore, the device also includes: an agent publishing module, which is also 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 ESB to query whether the host service is available.

[0183] Furthermore, the link management module is also used to trigger the proxy publishing module when it is found that the host service is unavailable or an exit signal is received;

[0184] 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 removes the attribute information of the host service from the service directory and completes the service deregistration.

[0185] Furthermore, the device also includes:

[0186] The node 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.

[0187] Furthermore, the device also includes:

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

[0189] 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.

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

[0191] Furthermore, the device also includes:

[0192] The data forwarding module is 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.

[0193] Based on the same inventive concept as the above disclosed content, the present disclosure also provides an electronic device accordingly. The electronic device of the present disclosure embodiment includes at least one processor and at least one memory electrically connected, the memory is electrically connected to the processor, wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can perform the method as described above.

[0194] It should be noted that the electrical connection between the above-mentioned units does not necessarily mean the connection between lines. An indirect connection method can be applied to the embodiments of the present disclosure as long as the purpose of the present disclosure is achieved.

[0195] Based on the same inventive concept, the present disclosure also provides a computer storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of the above method are implemented.

[0196] Although the present disclosure has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present 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, define and save the correspondence between the host service name and the grouped MATIP link resources according to the grouping information of the MATIP link resources in the configuration information, and create metadata corresponding to the host service; create MATIP connections in sequence according to the grouped MATIP link resources; 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, call the SOA architecture service directory interface through 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, characterized in that: The MATIP gateway is also used to monitor changes in MATIP link resource information; when adding, start a new MATIP connection and add the new MATIP connection to the grouped MATIP link resources corresponding to a host service name; when deleting, terminate the MATIP connection corresponding to the deleted MATIP link resource and remove it from the MATIP link group resources of the corresponding host service; provide host service status query according to the status of the grouped MATIP link.

3. The service processing system according to claim 2, characterized in that: 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 also used to determine the state of the ESB node based on the detection results of the IP address and service port of the ESB node; and / or determine the state of the ESB node 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.

6. The service processing system according to claim 1, characterized in that: 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 an open service request message carrying a 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 used 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 by using a stored correspondence between the host service name and the grouped MATIP link resources, select a MATIP link from the obtained MATIP link list, and forward the open service request message to the target host service processing node by 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 used 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 an open service response message to the MATIP gateway.

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

8. The service processing system according to claim 1, characterized in that: 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; 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 used 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 used to receive the host service request message, search for a service name matching the target open service name in the service directory, and then determine the 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 receiving and forwarding host service response messages to the MATIP gateway; The open service processing node is used to receive a host service request message sent by an ESB node, process the host service request message, obtain a host service response message, and send a 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 before forwarding request messages and response messages. 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; 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 certain host service name; when deleting, the MATIP connection corresponding to the deleted MATIP link resource is terminated and removed from the MATIP link grouping resource of the corresponding host service; Provide host service status query based on the status of the packet MATIP link.

12. The method according to claim 11, characterized in that Based on the attribute information of the host service, before calling the SOA architecture service catalog interface through the ESB, 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 the ESB so that the SOA architecture service directory interface removes the attribute information of the host service from the service directory and completes 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 an open service request message; Using the saved correspondence between the host service name and the 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 acquired MATIP link list, and use the selected MATIP link to forward the open service request message to the target host service processing node; 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 according to the load balancing policy and MATIP link status.

17. The method according to claim 10, characterized in that The method further comprises: Receive a host service request message carrying a 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 ESB nodes to host service processing nodes.

18. The method according to any one of claims 15 to 17, characterized in that: The method further comprises: Before forwarding the request message and response message, 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 comprises: a configuration management module, a link management module and an agent publishing module; wherein: A configuration management module, used to detect and load configuration information of a host service, wherein the configuration information includes: grouping information of MATIP link resources between a MATIP gateway and a 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 create MATIP connections in sequence 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 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 also used to monitor changes in MATIP link resource information; when adding, start a new MATIP connection and add the new MATIP connection to the grouped MATIP link resources corresponding to a host service name; when deleting, terminate the MATIP connection corresponding to the deleted MATIP link resource and remove it from the MATIP link group resources of the corresponding host service; provide host service status query according to 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 also 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 also used to trigger the proxy publishing module when it is found that the host service is unavailable or an exit signal is received; 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 removes the attribute information of the host service from the service directory and completes the service deregistration.

23. The device according to any one of claims 19 to 21, characterized in that: The device also includes: The node 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 also includes: The data forwarding module is used to receive an open service request message, select a MATIP link from the acquired MATIP link list, and forward the open service request message to the target host service processing node using the selected MATIP link; receive an 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 used to select a MATIP link from the acquired MATIP link list according to the load balancing strategy and the MATIP link status.

26. The device according to claim 19, characterized in that The device also includes: 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: The invention comprises at least one processor and at least one storage medium which are electrically connected; the storage medium is 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 so that the at least one processor can execute the service processing method according to any one of claims 10-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 as described in any one of claims 10-18.

Images