Standardized extensible method and system for accessing multiple services

Abstract

The invention provides a standardized extensible method and system for accessing multiple services, and aims to overcome the defect that a special protocol cannot be flexibly adapted when an existing service gateway accesses the services, various services needing to be accessed are directly accessed to the service gateway in a mode of adapting a professional protocol service plug-in and a general protocol service plug-in, and the service access efficiency is improved. According to the invention, an additional API interface does not need to be developed, the adaptability of the service gateway to various services is greatly enhanced, the service adaptation process is simplified through a standardized plug-in development specification, the development cost of service adaptation and the access difficulty of a service user are reduced, the service is convenient to popularize and apply, and the application range of the service gateway is widened. And the service access efficiency and the overall service management efficiency of the project are improved.

Description

Technical Field

[0001] This application relates to the fields of service gateways and computer technology, specifically to a standardized and scalable method and system for accessing multiple services. Background Technology

[0002] The service gateway is the single entry point in a microservice architecture. All external client requests must first pass through the service gateway. The main function of the service gateway is service access and service sharing. Existing services are connected to the service gateway through certain access specifications. The service gateway parses, encapsulates, and forwards the services to form new unified service formats and publishes them for easy use by other systems or individuals. Users do not need to care about the actual service access requirements and access methods. They only need to use the service gateway system to call the capabilities of various services, which greatly simplifies the adaptation of existing services and improves development efficiency and work effectiveness.

[0003] In current technologies, more and more services are provided via HTTP APIs, using JSON as the data structure for data transmission. This facilitates communication between services and systems. Most service gateways connect to services in the form of HTTP APIs. However, some older systems or modular services cannot provide API interfaces or other non-HTTP protocol services. In these cases, independent API interfaces must be developed and services must be connected according to the service gateway's access specifications. After being parsed, encapsulated, and converted by the service gateway, a unified external request format is formed before it can be provided to the requesting party.

[0004] Therefore, existing service gateways suffer from high service access costs, low service governance efficiency, and difficulty in accessing services for users. Based on the above problems, this application proposes a standardized and scalable method and system for accessing multiple services. Summary of the Invention

[0005] This application addresses one or more technical deficiencies in the prior art by proposing the following technical solution.

[0006] Based on the first aspect of this application, a standardized and scalable method for accessing multiple services is proposed, including:

[0007] S1: The service user initiates a service request to the service gateway, and the service gateway receives the service request and provides general protocol service plugins and dedicated protocol service plugin development tools;

[0008] S2: When the service gateway accesses the general protocol service, the service provider selects the corresponding protocol and configures the service parameters according to the type of the general protocol service. The service gateway encapsulates, routes, forwards, and converts the data format of the accessed general protocol service. The service gateway publishes the general protocol service.

[0009] S3: When the service gateway accesses the dedicated protocol service, the service provider packages the plugin components into a JAR file using the dedicated protocol service plugin development tool, obtains the plugin package, and uploads it to the service gateway. The service gateway reviews the code of the plugin package and publishes the plugin. The service provider fills in the key information and call reference information of the original service communication according to the plugin. The service gateway sets the route of the dedicated protocol service and binds the route to the corresponding plugin. The service gateway publishes the dedicated protocol service.

[0010] S4: The service gateway returns the service request result to the service user.

[0011] This application achieves unified access and governance of various heterogeneous services by connecting general protocol services and special protocol services to the service gateway in the form of standardized plug-ins. Service providers do not need to develop separate API interfaces for each service, which significantly reduces the complexity and development cost of service access, while improving the scalability and adaptability of the service gateway.

[0012] Furthermore, the general protocol service plugins include FTP service, email service, WEBSERVICE service, HTTPS service, WEBSOCKET service, and queue service.

[0013] This application enables service gateways to quickly adapt to common protocol services, reducing repetitive development work and improving the access efficiency of common protocol services.

[0014] Furthermore, the service parameters include connection parameters, authentication information, a request data example and a request data description, a return data example and a return data description.

[0015] This step makes the service access process more standardized and transparent, which is beneficial for understanding and using the service.

[0016] Furthermore, the dedicated protocol service plugin development tool includes a conversion interface, a routing and forwarding interface, and an original service adaptation interface;

[0017] The conversion interface is used to convert the format of request parameters and return parameters;

[0018] The routing forwarding interface is used to determine the access route for the service;

[0019] The original service adaptation interface is used to receive service request messages and interact with the original service.

[0020] This step enables service providers to flexibly develop custom plugins, enabling rapid access to non-standard proprietary protocol services and enhancing the protocol compatibility of the service gateway.

[0021] Furthermore, in steps S2 and S3, the general protocol service and the proprietary protocol service published by the service gateway are both in standard HTTP API format, and the request bodies are both in JSON format.

[0022] This step lowers the barrier to entry, making it easier to promote the service and integrate it across systems.

[0023] Furthermore, in step S4, when processing a general protocol service request, the service gateway verifies the basic parameters of the service request, converts the service request message into the form required by the original service, performs protocol conversion and authentication adaptation, forwards the service message request to the original service, and finally returns the service request result to the service user.

[0024] This step ensures that service requests are correctly forwarded to the original service, improving the reliability and security of service calls.

[0025] Furthermore, in step S4, when the service gateway processes a service request accessed through the dedicated protocol service plugin, it queries the routing information of the service request and dynamically loads the development tools in the dedicated protocol service plugin. It then converts the request parameters of the service request message through the conversion interface, finds the original service adaptation interface through the routing forwarding interface, and the original service adaptation interface interacts the service request message with the original service. Finally, it converts the return result of the original service into JSON format through the conversion interface and returns it to the service user.

[0026] This step enables transparent invocation of dedicated protocol services, ensuring flexibility and response efficiency in service calls.

[0027] Based on the second aspect of this application, a standardized and scalable system for accessing multiple services is also proposed, including:

[0028] Initiation module: Service users initiate service requests to the service gateway, and the service gateway receives the service requests and provides general protocol service plugins and special protocol service plugin development tools;

[0029] General module: When the service gateway accesses the general protocol service, the service provider selects the corresponding protocol and configures the service parameters according to the type of the general protocol service. The service gateway encapsulates, routes, forwards, and converts the data format of the accessed general protocol service. The service gateway publishes the general protocol service.

[0030] Dedicated Module: When the service gateway accesses the dedicated protocol service, the service provider packages the plugin components into a JAR file using the dedicated protocol service plugin development tool, obtains the plugin package, and uploads it to the service gateway. The service gateway reviews the code of the plugin package and publishes the plugin. The service provider fills in the key information and call reference information of the original service communication according to the plugin. The service gateway sets the route of the dedicated protocol service and binds the route to the corresponding plugin. The service gateway publishes the dedicated protocol service.

[0031] Return module: The service gateway returns the service request result to the service user.

[0032] Based on a third aspect of this application, a computer program product is also proposed, having one or more computer programs thereon that, when executed by a computer processor, perform the method as described in any of the above.

[0033] The technical advantages of this application are as follows: Addressing the shortcomings of existing service gateways in flexibly adapting to dedicated protocols when accessing services, this application utilizes professional protocol service plugins and general protocol service plugins for adaptation. This allows various services to be directly connected to the service gateway without the need to develop additional API interfaces, significantly enhancing the service gateway's adaptability to various services. Furthermore, standardized plugin development specifications simplify the service adaptation process, reduce development costs, and lower the access difficulty for service users, facilitating service promotion and application, and improving service access efficiency and overall project service governance efficiency. Attached Figure Description

[0034] Other features, objects, and advantages of this application will become more apparent from the following detailed description of non-limiting embodiments with reference to the accompanying drawings.

[0035] Figure 1 This is a flowchart illustrating a standardized and scalable method for accessing multiple services according to an embodiment of this application.

[0036] Figure 2 This is a standardized and scalable module diagram for accessing multiple service systems according to an embodiment of this application.

[0037] Figure 3 This is a standardized and scalable overall operational architecture diagram for accessing multiple service systems, provided according to an embodiment of this application.

[0038] Figure 4 This is a schematic diagram of the structure of a computer system suitable for implementing the electronic devices of the present application embodiments. Detailed Implementation

[0039] The present application will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, only the parts relevant to the invention are shown in the accompanying drawings.

[0040] It should be noted that, unless otherwise specified, the embodiments and features described in this application can be combined with each other. This application will now be described in detail with reference to the accompanying drawings and embodiments.

[0041] Figure 1 This application illustrates a standardized and scalable method for accessing multiple services, including:

[0042] S1: The service user initiates a service request to the service gateway, and the service gateway receives the service request and provides general protocol service plugins and dedicated protocol service plugin development tools;

[0043] S2: When the service gateway accesses the general protocol service, the service provider selects the corresponding protocol and configures the service parameters according to the type of the general protocol service. The service gateway encapsulates, routes, forwards, and converts the data format of the accessed general protocol service. The service gateway publishes the general protocol service.

[0044] S3: When the service gateway accesses the dedicated protocol service, the service provider packages the plugin components into a JAR file using the dedicated protocol service plugin development tool, obtains the plugin package, and uploads it to the service gateway. The service gateway reviews the code of the plugin package and publishes the plugin. The service provider fills in the key information and call reference information of the original service communication according to the plugin. The service gateway sets the route of the dedicated protocol service and binds the route to the corresponding plugin. The service gateway publishes the dedicated protocol service.

[0045] S4: The service gateway returns the service request result to the service user.

[0046] It should be noted that this application achieves unified access and governance of various heterogeneous services by connecting general protocol services and special protocol services to the service gateway in the form of standardized plug-ins. Service providers do not need to develop separate API interfaces for each service, which significantly reduces the complexity and development cost of service access, while improving the scalability and adaptability of the service gateway.

[0047] It should be noted that the general protocol service plugins include FTP service, email service, WEBSERVICE service, HTTPS service, WEBSOCKET service, and queue service.

[0048] It should be noted that this application enables service gateways to quickly adapt to common protocol services, reduce repetitive development work, and improve the access efficiency of common protocol services.

[0049] It should be noted that the service parameters include connection parameters, authentication information, a request data example and a request data description, a return data example and a return data description.

[0050] It should be noted that this step makes the service access process more standardized and transparent, which is beneficial for understanding and using the service.

[0051] It should be noted that the dedicated protocol service plugin development tool includes a conversion interface, a routing and forwarding interface, and an original service adaptation interface;

[0052] The conversion interface is used to convert the format of request parameters and return parameters;

[0053] The routing forwarding interface is used to determine the access route for the service;

[0054] The original service adaptation interface is used to receive service request messages and interact with the original service.

[0055] It should be noted that this step enables service providers to flexibly develop customized plugins, enabling rapid access to non-standard proprietary protocol services and enhancing the protocol compatibility of the service gateway.

[0056] It should be noted that in steps S2 and S3, the general protocol service and the proprietary protocol service published by the service gateway are both in standard HTTP API format, and the request bodies are both in JSON format.

[0057] It should be noted that this step lowers the barrier to entry, making it easier to promote the service and integrate it across systems.

[0058] It should be noted that in step S4, when the service gateway processes the general protocol service request, it verifies the basic parameters of the service request, converts the service request message into the form required by the original service, performs protocol conversion and authentication adaptation, forwards the service message request to the original service, and finally returns the service request result to the service user.

[0059] It should be noted that this step ensures that the service request can be correctly forwarded to the original service, thereby improving the reliability and security of the service call.

[0060] It should be noted that in step S4, when the service gateway processes a service request accessed through the dedicated protocol service plugin, it queries the routing information of the service request and dynamically loads the development tools in the dedicated protocol service plugin. It converts the request parameters of the service request message through the conversion interface, finds the original service adaptation interface through the routing forwarding interface, and the original service adaptation interface interacts the service request message with the original service. It also converts the return result of the original service into JSON format through the conversion interface and returns it to the service user.

[0061] It should be noted that this step enables transparent invocation of dedicated protocol services, ensuring the flexibility and response efficiency of service invocation.

[0062] The following is for reference. Figure 2 , Figure 2 A standardized and scalable system for accessing multiple services is shown, including an initiation module a, a general module b, a special module c, and a return module d.

[0063] In a specific embodiment, the initiating module a is configured to: the service user initiates a service request to the service gateway, and the service gateway receives the service request and provides a general protocol service plugin and a dedicated protocol service plugin development tool.

[0064] In a specific embodiment, the general module b is configured as follows: when the service gateway accesses the general protocol service, the service provider selects the corresponding protocol and configures the service parameters according to the type of the general protocol service; the service gateway encapsulates, routes, forwards, and converts the data format of the accessed general protocol service; and the service gateway publishes the general protocol service.

[0065] In a specific embodiment, the dedicated module c is configured as follows: when the service gateway accesses the dedicated protocol service, the service provider packages the plugin components into a JAR file using the dedicated protocol service plugin development tool, obtains the plugin package, and uploads it to the service gateway. The service gateway reviews the code of the plugin package and publishes the plugin. The service provider fills in the key information and call reference information of the original service communication according to the plugin. The service gateway sets the route of the dedicated protocol service and binds the route to the corresponding plugin. The service gateway publishes the dedicated protocol service.

[0066] In a specific embodiment, the return module d is configured such that the service gateway returns the service request result to the service user.

[0067] In a specific embodiment, the overall operating architecture of the standardized and scalable system for accessing multiple services is as follows: Figure 3 As shown:

[0068] When accessing a general protocol service, service gateway 302 provides general protocol service plugin 303, which includes FTP service, email service, WEBSERVICE service, HTTPS service, WEBSOCKET service, and queue service (including Kafka and ActiveMQ).

[0069] Service providers access services through service gateway 302 according to the type of general protocol service, and select the corresponding protocol to fill in the service parameters, including relevant connection parameters, authentication information, request data example, request data description, return data example and return data description;

[0070] When Service Gateway 302 receives access information for the general protocol service, it encapsulates and routes the service request, converts the request and return parameters into JSON format, and publishes the processed general protocol service as a standard HTTP API service with the request body uniformly in JSON format.

[0071] After the service user 301 submits an application, it makes a service request based on the information displayed on the page. After receiving the user's request, the service gateway 302 verifies the basic parameters, converts the request message into the form required by the original service, performs protocol conversion and authentication adaptation, and then forwards the service request message to the original service and returns the result to the service user 301.

[0072] When accessing a dedicated protocol service, the service provider downloads the service protocol plugin development package and development manual 304 from the service gateway 302. The package contains three core interfaces: conversion interface, routing forwarding interface, and original service adaptation interface. The service provider packages the core interfaces into a jar plugin package according to the development package and development manual, uploads it to the service gateway 302, and fills in the relevant service information. The service gateway 302 reviews the plugin package and releases it.

[0073] When a service provider accesses a service through a service gateway, it selects the appropriate service plugin, fills in the key information for communication with the original service according to the plugin's requirements, and also fills in the reference information for user calls. After receiving the service access information, the service gateway 302 sets the service route, binds the plugin and the route, and then publishes the service using the standard API interface, with the request body using the standard JSON format.

[0074] After service user 301's service application is approved, the user follows the on-screen instructions to make the request. Upon receiving the service request, service gateway 302 queries the service's route, dynamically loads the core interfaces in the plugin, converts the request parameters through a conversion interface, finds the original service adaptation interface through the route conversion interface, the original service adaptation interface carries the converted message, interacts with the original service, and forwards the returned message to the conversion interface. The conversion interface converts the returned message into a JSON format message and returns it to service user 301.

[0075] It should be noted that this application achieves unified access and governance of various heterogeneous services by connecting general protocol services and special protocol services to the service gateway in the form of standardized plug-ins. Service providers do not need to develop separate API interfaces for each service, which significantly reduces the complexity and development cost of service access, while improving the scalability and adaptability of the service gateway.

[0076] The following is for reference. Figure 4 It shows a schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application. Figure 4 The electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0077] like Figure 4 As shown, the computer system includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 402 or programs loaded from storage section 408 into random access memory (RAM) 403. RAM 403 also stores various programs and data required for system operation. CPU 401, ROM 402, and RAM 403 are interconnected via bus 404. Input / output (I / O) interface 405 is also connected to bus 404.

[0078] The following components are connected to I / O interface 405: an input section 406 including a keyboard, mouse, etc.; an output section 407 including a liquid crystal display (LCD) and speakers, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN card and a modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to I / O interface 405 as needed. A removable medium 411, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 410 as needed so that computer programs read from it can be installed into storage section 408 as needed.

[0079] Specifically, according to embodiments of this disclosure, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this disclosure include a computer program product comprising a computer program carried on a computer-readable storage medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411. When the computer program is executed by central processing unit (CPU) 401, it performs the functions defined in the methods of this application. It should be noted that the computer-readable storage medium of this application can be a computer-readable signal medium or a computer-readable storage medium or any combination thereof. The computer-readable storage medium can be, for example,—but not limited to—an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this application, a computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium can also be any computer-readable storage medium other than a computer-readable storage medium that can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. Program code contained on a computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical fiber, RF, etc., or any suitable combination thereof.

[0080] Computer program code for performing the operations of this application can be written in one or more programming languages ​​or a combination thereof. Programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—as well as conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0081] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0082] The modules described in the embodiments of this application can be implemented in software or in hardware.

[0083] In another aspect, this application also provides a computer-readable storage medium, which may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable storage medium carries one or more programs. When the electronic device executes the aforementioned one or more programs, the electronic device causes the following: a service user initiates a service request to the service gateway, and the service gateway receives the service request; when the service gateway accesses a general protocol service, the service provider selects the corresponding protocol and configures service parameters according to the type of the general protocol service; the service gateway encapsulates, routes, and converts the data format of the accessed general protocol service; and the service gateway publishes the general protocol service; when the service gateway accesses a dedicated protocol service, the service provider packages the plugin components into a JAR file using a dedicated protocol service plugin development tool, obtains the plugin package, and uploads it to the service gateway; the service gateway reviews the code of the plugin package and publishes the plugin; the service provider fills in the key information and call reference information of the original service communication according to the plugin; the service gateway sets the route of the dedicated protocol service and binds the route to the corresponding plugin; and the service gateway publishes the dedicated protocol service; and the service gateway returns the service request result to the service user.

[0084] Finally, it should be noted that the above description is merely a preferred embodiment of this application and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this application is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the above-described inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features with similar functions disclosed in this application.

Claims

1. A standardized and scalable method for accessing multiple services, characterized in that, include: S1: The service user initiates a service request to the service gateway, and the service gateway receives the service request and provides general protocol service plugins and dedicated protocol service plugin development tools; S2: When the service gateway accesses the general protocol service, the service provider selects the corresponding protocol and configures the service parameters according to the type of the general protocol service. The service gateway encapsulates, routes, forwards, and converts the data format of the accessed general protocol service. The service gateway publishes the general protocol service. S3: When the service gateway accesses the dedicated protocol service, the service provider packages the plugin components into a JAR file using the dedicated protocol service plugin development tool, obtains the plugin package, and uploads it to the service gateway. The service gateway reviews the code of the plugin package and publishes the plugin. The service provider fills in the key information and call reference information of the original service communication according to the plugin. The service gateway sets the route of the dedicated protocol service and binds the route to the corresponding plugin. The service gateway publishes the dedicated protocol service. S4: The service gateway returns the service request result to the service user.

2. The method according to claim 1, characterized in that, The general protocol service plugins include FTP service, email service, WEBSERVICE service, HTTPS service, WEBSOCKET service, and queue service.

3. The method according to claim 1, characterized in that, The service parameters include connection parameters, authentication information, a request data example and a request data description, a return data example and a return data description.

4. The method according to claim 1, characterized in that, The dedicated protocol service plugin development tool includes a conversion interface, a routing and forwarding interface, and a raw service adaptation interface. The conversion interface is used to convert the format of request parameters and return parameters; The routing forwarding interface is used to determine the access route for the service; The original service adaptation interface is used to receive service request messages and interact with the original service.

5. The method according to claim 1, characterized in that, In steps S2 and S3, the general protocol service and the proprietary protocol service published by the service gateway are both in standard HTTP API format, and the request bodies are both in JSON format.

6. The method according to claim 1, characterized in that, In step S4, when processing a general protocol service request, the service gateway verifies the basic parameters of the service request, converts the service request message into the form required by the original service, performs protocol conversion and authentication adaptation, forwards the service message request to the original service, and finally returns the service request result to the service user.

7. The method according to claim 1, characterized in that, In step S4, when the service gateway processes a service request accessed through a dedicated protocol service plugin, it queries the routing information of the service request and dynamically loads the development tools in the dedicated protocol service plugin. It then converts the request parameters of the service request message through the conversion interface, finds the original service adaptation interface through the routing forwarding interface, and the original service adaptation interface interacts the service request message with the original service. Finally, it converts the return result of the original service into JSON format through the conversion interface and returns it to the service user.

8. A standardized and scalable system for accessing multiple services, characterized in that, include: Initiation module: Service users initiate service requests to the service gateway, and the service gateway receives the service requests and provides general protocol service plugins and special protocol service plugin development tools; General module: When the service gateway accesses the general protocol service, the service provider selects the corresponding protocol and configures the service parameters according to the type of the general protocol service. The service gateway encapsulates, routes, forwards, and converts the data format of the accessed general protocol service. The service gateway publishes the general protocol service. Dedicated Module: When the service gateway accesses the dedicated protocol service, the service provider packages the plugin components into a JAR file using the dedicated protocol service plugin development tool, obtains the plugin package, and uploads it to the service gateway. The service gateway reviews the code of the plugin package and publishes the plugin. The service provider fills in the key information and call reference information of the original service communication according to the plugin. The service gateway sets the route of the dedicated protocol service and binds the route to the corresponding plugin. The service gateway publishes the dedicated protocol service. Return module: The service gateway returns the service request result to the service user.

9. A computer program product having one or more computer programs thereon, characterized in that, When the computer program is executed by a computer processor, the method described in any one of claims 1-7 is performed.

Images