Protocol gateway architecture, client communication method and device, and storage medium

Abstract

The invention relates to the technical field of computers, and particularly discloses a protocol gateway architecture, a client communication method and device and a storage medium, the protocol gateway architecture comprises a protocol client layer, a protocol conversion layer and an internal service layer, the protocol client layer comprises a plurality of external clients of different protocol types, and the internal service layer comprises a plurality of external clients of different protocol types. The external client is connected with the server with the same protocol type; the protocol conversion layer is connected with external clients and used for converting data sent by the external clients into internal services or external services and forwarding the external services to the protocol client layer through protocol routing so as to complete communication between different external clients; and the internal service layer is connected with the protocol conversion layer and is used for converting the internal service into a service of a protocol which can be identified by at least one internal client and forwarding the service to the at least one internal client so as to realize mutual conversion among different protocol types and enable different types of clients to communicate with each other.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer technology, and in particular to a protocol gateway architecture, a client communication method and device, and a storage medium. BACKGROUND

[0002] Protocol conversion is widely used in client communication, which can enable smooth interaction between clients. Some hardware gateway devices have the ability of protocol conversion, which can convert the modbus protocol into the http (HyperText Transfer Protocol, HyperText Transfer Protocol) or mqtt (Message Queuing Telemetry Transport, Message Queuing Telemetry Transport) protocol and communicate with the cloud. However, the hardware gateway device needs to expose its own data and protocol to third-party devices, which has security risks. Therefore, a soft gateway emerges as the times require, which can reduce the cost, reduce the installation space, and has high security performance.

[0003] In the related art, the soft gateway only supports the conversion of someip (Scalable service-Oriented MiddlewarE over IP, Scalable service-Oriented MiddlewarE over IP) protocol and DDS (Data Distribution Service, Data Distribution Service) protocol into MQTT, and the data used is based on the MQTT protocol to interact with the cloud, and it does not support the mutual conversion between any two protocols, which greatly limits the gateway function. SUMMARY

[0004] The present application aims to at least solve one of the technical problems in the related art. To this end, the first purpose of the present application is to propose a protocol gateway architecture, which can realize the mutual conversion between different protocol types, so that different types of clients can communicate with each other, and improve the compatibility of the gateway architecture for protocol types.

[0005] The second purpose of the present application is to propose a client communication method.

[0006] The third purpose of the present application is to propose a computer-readable storage medium.

[0007] The fourth purpose of the present application is to propose a client communication device.

[0008] To achieve the above object, the protocol gateway architecture according to an embodiment of the present application comprises a protocol client layer, a protocol conversion layer and an internal service layer, wherein the protocol client layer comprises a plurality of external clients of different protocol types, the external clients being connected with service ends of the same protocol type; the protocol conversion layer is connected with the external clients, and is configured to convert data sent by the external clients into internal services or external services, and forward the external services to the protocol client layer through protocol routing to complete communication between different external clients; the internal service layer is connected with the protocol conversion layer, and is configured to convert the internal services into services of at least one protocol recognizable by internal clients, and forward the services to the at least one internal client to complete communication between the internal clients and the external clients.

[0009] The protocol gateway architecture according to an embodiment of the present application comprises a protocol client layer, a protocol conversion layer and an internal service layer, the protocol conversion layer being connected with the internal service layer and external clients in the protocol client layer, the external clients being capable of sending data to the protocol conversion layer, so that the protocol conversion layer converts the data into internal services or external services, if the data is external services, the protocol conversion layer forwards the external services to the protocol client layer through protocol routing, and then completes protocol conversion to enable different clients to communicate with each other; if the data is internal services, the internal services are sent to the internal service layer, and the internal service layer converts the internal services into services of at least one protocol recognizable by internal clients, and then forwards the services to the internal clients, thereby completing communication between the internal clients and the external clients. Thus, the protocol gateway architecture according to the present application can convert different protocol types, so that different types of clients can communicate with each other, and the compatibility of the gateway architecture for protocol types is improved.

[0010] In some embodiments of the present application, the internal service layer is further configured to convert data sent by a plurality of internal clients and send the data to the protocol conversion layer, so that the data is converted into services of at least one protocol recognizable by external clients through the protocol conversion layer.

[0011] In some embodiments of the present application, the internal service layer and the internal clients are connected through a service-oriented architecture to complete publication and subscription.

[0012] In some embodiments of the present application, the internal service layer is connected with the internal clients of different calling interfaces through communication middleware.

[0013] In some embodiments of the present application, the external client downloads a configuration file before connecting to the server of the same protocol type, the configuration file including the type and number of the external client, parameters for the external client to establish a connection with the server of the same protocol type, forwarding rules and routing rules of the protocol conversion layer, and service parameters of the internal service layer.

[0014] In some embodiments of the present application, the external client performs fault tolerance processing after connecting to the server of the same protocol type, to determine whether the external client successfully establishes a connection with the server of the same protocol type.

[0015] In some embodiments of the present application, the protocol conversion layer converts the data sent by the external client into the internal service when detecting that the data sent by the external client includes preset parameters, and converts the data sent by the external client into the external service otherwise.

[0016] To achieve the above object, the second aspect of the present application provides a client communication method, which is implemented based on the protocol gateway architecture of any of the above embodiments, and the method comprises: acquiring data sent by a sending client in the external client and / or the internal client; converting the protocol type of the data by the protocol conversion layer and the internal service layer; and forwarding the converted data to a receiving client in the external client and / or the internal client, so as to complete communication between the sending client and the receiving client.

[0017] The client communication method of the embodiments of the present application is implemented based on the protocol gateway architecture in the above embodiments. The method first acquires data sent by a sending client in the external client and / or the internal client, then converts the protocol type of the data by the protocol conversion layer and the internal service layer, and sends the converted data to a receiving client in the external client and / or the internal client, thereby completing communication between the clients. Thus, the present application can realize mutual conversion between different protocol types, so that different types of clients can communicate with each other.

[0018] To achieve the above object, the third aspect of the present application provides a computer readable storage medium, which stores a client communication program, and the client communication program is executed by a processor to implement the client communication method of the above embodiments.

[0019] The computer readable storage medium of the embodiments of the present application stores the client communication program, which is executed by a processor to implement mutual conversion between different protocol types, so that different types of clients can communicate with each other.

[0020] To achieve the above object, the fourth aspect of the present application provides a client communication device, which is implemented based on the protocol gateway architecture of any of the above embodiments, and comprises an acquisition module, a conversion module and a sending module, wherein the acquisition module is configured to acquire data sent by a sending client in the external client and / or the internal client; the conversion module is configured to convert the protocol type of the data through the protocol conversion layer and the internal service layer; and the sending module is configured to forward the converted data to a receiving client in the external client and / or the internal client, so as to complete the communication between the sending client and the receiving client.

[0021] The client communication device of the embodiment of the present application is implemented based on the protocol gateway architecture in the above embodiments, which first acquires the data sent by the sending client in the external client and / or the internal client by using the acquisition module, then converts the protocol type of the data by using the conversion module through the protocol conversion layer and the internal service layer, and after the conversion is completed, sends the converted data to the receiving client in the external client and / or the internal client by using the sending module, thereby completing the communication between the clients. Thus, the present application can realize the mutual conversion between different protocol types, so that different types of clients can communicate with each other.

[0022] Additional aspects and advantages of the present application will be given in part in the following description, become apparent from the following description, or be understood through practice of the present application. BRIEF DESCRIPTION OF DRAWINGS

[0023] Figure 1 is a schematic diagram of the protocol gateway architecture in an embodiment of the present application;

[0024] Figure 2 is a schematic diagram of the protocol gateway architecture in another embodiment of the present application;

[0025] Figure 3 is a schematic diagram of the protocol conversion layer in a specific embodiment of the present application;

[0026] Figure 4 is a flow chart of the client communication method in an embodiment of the present application;

[0027] Figure 5 is a structural schematic diagram of the client communication device in an embodiment of the present application. DETAILED DESCRIPTION

[0028] Embodiments of the present application are described below in detail with reference to the accompanying drawings, examples of which are shown in the drawings, wherein the same or similar notations represent the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to explain the present application, and cannot be understood as a limitation of the present application.

[0029] The protocol gateway architecture, the client communication method and device, and the storage medium of the embodiments of the present application are described below with reference to the accompanying drawings.

[0030] Figure 1 is a schematic diagram of the protocol gateway architecture in one embodiment of the present application.

[0031] As shown in Figure 1 , the present application proposes a protocol gateway architecture, which includes a protocol client layer, a protocol conversion layer, and an internal service layer.

[0032] The protocol client layer includes a plurality of external clients of different protocol types, and the external clients are connected with service ends of the same protocol type; the protocol conversion layer is connected with the external clients, and is configured to convert data sent by the external clients into internal services or external services, and forward the external services to the protocol client layer through protocol routing to complete communication between different external clients; the internal service layer is connected with the protocol conversion layer, and is configured to convert the internal services into services of at least one protocol recognizable by internal clients and forward the services to the at least one internal client to complete communication between the internal clients and the external clients.

[0033] Specifically, the protocol client layer in the present embodiment can include a plurality of external clients, and each external client can correspond to a different protocol type, for example Figure 1 MQTT client, SOMEIP client, DDS client, etc., and it should be noted that the XXX client in the figure can represent a client of other protocol types. Each client is also connected with a corresponding service end (not shown in the figure), for example, the MQTT client is connected with the MQTT service end, the SOMEIP client is connected with the SOMEIP service end, and the DDS client is connected with the DDS service end, and other protocol clients with similar mechanisms can also be processed in the same way. The protocol client layer can communicate with external systems through external client load, the protocol conversion layer can be responsible for converting data between different protocols, and the internal service layer can provide specific business logic and services.

[0034] More specifically, when two external clients of different protocol types need to communicate, the sending client sends the data to be interacted to the protocol conversion layer, the protocol conversion layer performs protocol conversion after receiving the data to convert into a protocol recognizable by the receiving client, and then sends the data to the receiving client through protocol routing, thereby completing the communication between the external clients of different protocol types. When the external client and the internal client of different protocol types need to communicate, taking the external client sending interaction data to the internal client as an example, the external client first sends the data to be interacted to the protocol conversion layer, the protocol conversion layer performs protocol conversion after receiving the data, and sends the converted internal service to the internal service layer, the internal service layer further converts, and finally sends the converted information to the internal client, thereby completing the information interaction between the internal client and the external client. It should be noted that the sending client and the receiving client can be one-to-one, one-to-many or many-to-one, that is, the protocol conversion layer and the internal service layer can convert one external service into multiple internal services, or combine multiple external services into one internal service. Of course, in the process of communication of the external client, one service of one external client can also be converted into multiple services of another external client or multiple services of multiple external clients, or multiple services of multiple external clients or multiple services of one external client can be combined into one service of another client, and the specific selection can be made according to the application scenario.

[0035] In some embodiments of the application, the internal service layer is further configured to convert and send the data sent by the plurality of internal clients to the protocol conversion layer, so as to convert at least one external client recognizable protocol service through the protocol conversion layer.

[0036] Specifically, as shown in Figure 2 The internal client can include APP Client1, APP Client2, APP Clientx, each internal client is connected with the internal service layer, the internal service layer can convert the data sent by the plurality of internal clients, and send the converted data to the protocol conversion layer, the protocol conversion layer can further convert the received data into a service corresponding to a protocol recognizable by the external client, and send it to the external client, so as to complete the communication between the internal client and the external client, and increase the communication mode. It should be noted that the data of one internal client can be sent to one or more external clients at a time, and the data of multiple internal clients can be sent to one external client at a time. It can be understood that the data described in the above embodiments can be a functional service.

[0037] In this embodiment, the internal service layer and the internal client complete the publish and subscribe through a service-oriented architecture.

[0038] Specifically, such as Figure 2 As shown, the internal service layer and the internal client communicate using the SOA communication middleware, which can also operate in a publish / subscribe mode. In the publish / subscribe mode, publishers and subscribers are associated through topics. Neither party needs to know the other's location or be online at the same time, achieving multidimensional loose coupling in terms of time, space, and data communication.

[0039] In this embodiment, the internal service layer establishes connections with internal clients that call different interfaces by setting up communication middleware.

[0040] Specifically, different internal clients may have different calling interfaces. In order for different calling interfaces to establish a connection with the internal service layer, this can be achieved by setting the parameters of the communication middleware.

[0041] In some embodiments of the present invention, the external client downloads a configuration file before connecting to a server of the same protocol type. The configuration file includes the type and number of external clients, parameters for establishing a connection between the external client and the server of the same protocol type, forwarding and routing rules of the protocol conversion layer, and service parameters of the internal service layer. After connecting to the server of the same protocol type, the external client also performs fault tolerance processing to ensure that the connection between the external client and the server of the same protocol type is successfully established.

[0042] During the connection process between external clients and corresponding servers, each external client can be configured first. This can be done by downloading a configuration file, which includes the type and number of external clients, the parameters required for establishing a connection between the external client and the corresponding server, the forwarding and routing rules of the protocol conversion layer, and the service parameters of the internal service layer.

[0043] The following is the code information of the configuration file in a specific embodiment:

[0044] Configuration file:

[0045] MQTT Client1:

[0046] config:

[0047] {

[0048] Enable Flag:

[0049] server IP:

[0050] server port:

[0051] username=""

[0052] password=""

[0053] }

[0054] Rule 1:

[0055] {

[0056] From Topic: The topic that needs to be converted

[0057] To Topic: Converted topic

[0058] Switch Protocol: The converted protocol

[0059] Route Flag: 0: Route, 1: Internal, 2: Route + Internal

[0060] Route configuration: [IP address: xx xx xx xx, Port: xx]

[0061] Iswitch Type:[]: Internal service switch type

[0062] }

[0063] The above is just a partial code demonstration of a specific embodiment, and the configuration file can be adapted to meet specific needs in specific use cases.

[0064] In this embodiment, after the external client establishes a connection with the corresponding server, due to the differences between devices of different models or even different manufacturers, fault tolerance processing is still required. Specifically, it can be adjusted according to the communication results between the external client and the server to ensure that the external client and the corresponding server can successfully establish a connection.

[0065] In some embodiments of the present invention, when the protocol conversion layer detects that the data sent by the external client includes preset parameters, it converts the data sent by the external client into an internal service; otherwise, it converts the data sent by the external client into an external service.

[0066] Specifically, the preset parameter in the embodiment can be searched and compared in the routing rule described in the above embodiment, wherein the corresponding flag bits of the routing rule are 0, 1 and 2, wherein 0 corresponds to external service, 1 corresponds to internal service, and 2 includes both external service and internal service. The preset parameter in the embodiment can be the parameter corresponding to the flag bit 1 in the routing rule, so when it is detected that the data sent by the external client includes the preset parameter, the data sent by the external client can be converted into internal service. Of course, in some embodiments, the corresponding flag bits of the routing rule can only include 0 and 1, so if it is detected that the data sent by the external client does not include the preset parameter, the data sent by the external client can be directly converted into external service.

[0067] Further, as shown in Figure 3 , From Topic, Data represents the data sent by the external client to the protocol conversion layer, the protocol conversion layer processes the data according to the configuration file, and when the processing is completed and it is determined that the data is external service, the protocol conversion layer directly forwards the data to other external clients by using the protocol conversion routing, and To Topic, Data represents the data that needs to be sent to the external client after processing. When the processing is completed and it is determined that the data is internal service, the data is sent to the internal service layer for further processing by the internal service layer, wherein To Topic, Data (Iswitch Type, Data) represents the data sent to the internal service layer. From Topic, Data: (Iswitch Type, Data) represents the data sent by the internal service layer to the protocol conversion layer, which is sent to the external client in the form of To Topic, Data after processing by the protocol conversion layer.

[0068] In summary, the protocol gateway architecture in the embodiment of the application can realize mutual conversion between different protocol types, so that different types of clients can communicate with each other, and the compatibility of the gateway architecture for protocol types is improved.

[0069] Figure 4 is a flowchart of the client communication method in the embodiment of the application.

[0070] Further, as shown in Figure 4 , the application provides a client communication method based on the protocol gateway architecture of any one of the above embodiments, the method comprising the following steps:

[0071] S10, acquiring the data sent by a sending client in an external client and / or an internal client.

[0072] S20, converting the protocol type of the data by the protocol conversion layer and the internal service layer.

[0073] S30 forwards the converted data to the external client and / or the receiving client among the internal clients, so that the sending client and the receiving client can complete communication.

[0074] The client communication method of this invention is implemented based on the protocol gateway architecture described in the above embodiments. This method first obtains data sent by the sending client in the external client and / or internal client, then uses a protocol conversion layer and an internal service layer to perform protocol type conversion on the data, and finally sends it to the receiving client in the external client and / or internal client after the conversion is complete, thereby completing communication between the clients. Therefore, this invention can realize mutual conversion between different protocol types, enabling communication between clients of different types.

[0075] It should be noted that the specific implementation of the client communication method in this embodiment of the invention can be found in the specific implementation of the protocol gateway architecture in the above embodiments. To avoid redundancy, it will not be described again here.

[0076] Furthermore, the present invention proposes a computer-readable storage medium storing a client communication program thereon, which, when executed by a processor, implements the client communication method of the above embodiments.

[0077] The computer-readable storage medium of this invention executes a client communication program stored thereon via a processor, enabling mutual conversion between different protocol types and allowing different types of clients to communicate with each other.

[0078] Figure 5 This is a schematic diagram of the structure of the client communication device in an embodiment of the present invention.

[0079] Furthermore, such as Figure 5 As shown, the present invention proposes a client communication device 100 based on the protocol gateway architecture of the above embodiments. The client communication device 100 includes an acquisition module 101, a conversion module 102 and a sending module 103.

[0080] The acquisition module 101 is used to acquire data sent by the sending client in the external client and / or internal client; the conversion module 102 is used to convert the protocol type of the data through the protocol conversion layer and the internal service layer; the sending module 103 forwards the converted data to the receiving client in the external client and / or internal client so that the sending client and the receiving client can complete communication.

[0081] The client communication device 100 of the embodiment of the present application is implemented based on the protocol gateway architecture in the above embodiment. The device 100 first acquires data sent by a sending client in the external client and / or the internal client by using the acquisition module 101, then converts the data by using the conversion module 102 to convert the protocol type of the data through the protocol conversion layer and the internal service layer, and after the conversion is completed, sends the converted data to a receiving client in the external client and / or the internal client by using the sending module 103, thereby completing the communication between the clients. Thus, the present application can realize the mutual conversion between different protocol types, so that the different types of clients can communicate with each other.

[0082] It should be noted that the specific implementation of the client communication device in the embodiment of the present application can refer to the specific implementation of the protocol gateway architecture in the above embodiment, and to avoid redundancy, will not be described here.

[0083] It should be noted that the logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a list of executable instructions for implementing logical functions, and can be specifically implemented in any computer readable medium for use by or in conjunction with an instruction execution system, device or apparatus, such as a computer-based system, a system including a processor or other system that can fetch and execute instructions from an instruction execution system, device or apparatus. For the purpose of the present specification, the "computer readable medium" can be any device that can contain, store, communicate, propagate or transport programs for use by or in conjunction with an instruction execution system, device or apparatus, or in conjunction with these instruction execution systems, devices or apparatus. More specific examples (non-exhaustive list) of computer readable medium include the following: electrical connections having one or more wires (electronic devices), portable computer disk boxes (magnetic devices), random access memories (RAM), read only memories (ROM), erasable programmable read only memories (EPROM or flash memory), fiber optic devices, and portable compact disc read only memories (CDROM). In addition, the computer readable medium can even be paper or other suitable medium on which the program can be printed, because the program can be obtained electronically, for example, by optical scanning of the paper or other medium, followed by editing, interpreting or otherwise processing, if necessary, in other suitable ways, to be stored in the computer memory.

[0084] It should be understood that various aspects of the application can be implemented in hardware, software, firmware or a combination of them. In the above embodiments, various steps or methods can be implemented in software or firmware which is stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, any of the following technologies, known in the art, or their combinations, can be employed: discrete logic circuitry having logic gates for implementing logic functions upon an application of data signals, application-specific integrated circuits having appropriate combinational logic gates, programmable gate arrays (PGA), field-programmable gate arrays (FPGA), and so on.

[0085] In the description of the present application, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" and the like means that a specific feature, structure, material or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. Descriptive terms of the above terms in the present specification do not necessarily refer to the same embodiment or example. Also, the described specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0086] In the description of the present application, it should be understood that the terms "center", "longitudinal", "lateral", "length", "width", "thickness", "upper", "lower", "front", "rear", "left", "right", "vertical", "horizontal", "top", "bottom", "inner", "outer", "clockwise", "counterclockwise", "axial", "radial", "circumferential" and the like indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, and are only for the convenience of describing the present application and simplifying the description, and do not indicate or imply that the device or element referred to must have a particular orientation, be constructed and operated in a particular orientation, and therefore cannot be understood as a limitation on the present application.

[0087] In addition, the terms "first", "second", and the like used in the embodiments of the present application are only for the purpose of description, and can not be understood as indicating or implying relative importance, or implicitly indicating the number of technical features referred to in the embodiments. Therefore, the features defined with "first", "second" and the like in the embodiments of the present application can be explicitly or implicitly indicated to include at least one of the features in the embodiments. In the description of the present application, the meaning of the word "plurality" is at least two or two or more, such as two, three, four, etc., unless otherwise specifically limited in the embodiments.

[0088] In the present application, unless otherwise explicitly specified or limited in the embodiments, the terms "mounting", "connecting", "connecting" and "fixing" and the like appearing in the embodiments should be understood broadly, for example, the connection can be fixed connection, or detachable connection, or integral, which can be understood, or mechanical connection, electrical connection, etc. Of course, it can also be directly connected, or indirectly connected through an intermediate medium, or the internal communication of two elements, or the interaction relationship of two elements. For those skilled in the art, the specific meaning of the above terms in the present application can be understood according to the specific implementation situation.

[0089] In the present application, unless otherwise explicitly specified and limited, the first feature is "on" or "under" the second feature. The first and second features can be in direct contact, or the first and second features can be indirectly contacted through an intermediate medium. Moreover, the first feature "above", "above" and "above" the second feature can be directly above or obliquely above the first feature, or only indicate that the horizontal height of the first feature is higher than that of the second feature. The first feature "below", "below" and "below" the second feature can be directly below or obliquely below the first feature, or only indicate that the horizontal height of the first feature is less than that of the second feature.

[0090] Although the embodiments of the present application have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present application. Those skilled in the art can make changes, modifications, replacements and variations to the above embodiments within the scope of the present application.

Claims

1. A protocol gateway architecture, characterized by The protocol gateway architecture comprises: a protocol client layer comprising a plurality of external clients of different protocol types, the external clients being connected to service ends of the same protocol type; a protocol conversion layer connected to the external clients, for converting data sent by the external clients into internal services or external services, and forwarding the external services to the protocol client layer through protocol routing to complete communication between different external clients; an internal service layer connected to the protocol conversion layer, for converting the internal services into services of at least one protocol recognizable by internal clients and forwarding the services to the internal clients to complete communication between the internal clients and the external clients.

2. The protocol gateway architecture of claim 1, wherein, The internal service layer is further configured to convert data sent by a plurality of the internal clients and send the data to the protocol conversion layer to be converted into services of at least one protocol recognizable by the external clients through the protocol conversion layer.

3. The protocol gateway architecture of claim 2, wherein, The internal service layer and the internal clients complete publication and subscription through a service-oriented architecture.

4. The protocol gateway architecture of claim 3, wherein, The internal service layer establishes connection with the internal clients of different calling interfaces through communication middleware.

5. The protocol gateway architecture of claim 1, wherein, The external clients perform configuration file downloading before being connected to service ends of the same protocol type, the configuration file comprising the type and quantity of the external clients, parameters for establishing connection between the external clients and service ends of the same protocol type, forwarding rules and routing rules of the protocol conversion layer, and service parameters of the internal service layer.

6. The protocol gateway architecture of claim 5, wherein, The external clients perform fault tolerance processing after being connected to service ends of the same protocol type to determine whether the external clients and service ends of the same protocol type successfully establish connection.

7. The protocol gateway architecture according to any of claims 1-6, characterized by, The protocol conversion layer converts data sent by the external clients into the internal services when the data sent by the external clients comprises preset parameters, and converts the data sent by the external clients into the external services otherwise.

8. A client communication method, comprising: The protocol gateway architecture implementation based on any one of claims 1-7, the method comprising: obtaining data sent by a sending client in the external clients and / or the internal clients; converting the protocol type of the data through the protocol conversion layer and the internal service layer; forwarding the converted data to a receiving client in the external clients and / or the internal clients to enable the sending client and the receiving client to complete communication.

9. A computer-readable storage medium, characterized in that, A computer readable storage medium having stored thereon a client communication program, the client communication program being executed by a processor to implement the client communication method of claim 8.

10. A client communication device, characterized by The protocol gateway architecture implementation based on any one of claims 1-7, the apparatus comprising: an obtaining module configured to obtain data sent by a sending client in the external clients and / or the internal clients; a conversion module configured to convert the protocol type of the data through the protocol conversion layer and the internal service layer; a forwarding module configured to forward the converted data to a receiving client in the external clients and / or the internal clients to enable the sending client and the receiving client to complete communication. The sending module forwards the converted data to a receiving client in the external client and / or the internal client, so that the sending client and the receiving client complete communication.

Images