Rsocket-based cross-server communication method, device and equipment, and storage medium

Abstract

Embodiments of the present application provide a cross-service communication method and device based on RSocket, equipment and a storage medium, the method comprising: receiving a connection request sent by a first client, the connection request recording node information of the first client, the node information comprising a role identifier and a node identifier; adding the node information to a routing table, the routing table recording node information sent by a plurality of different first clients; receiving a request message sent by a second client, determining a target node corresponding to the request message according to routing information recorded in the request message and node information recorded in the routing table, and forwarding the request message to the target node. The present scheme significantly reduces the resource consumption of communication between each service, and reduces the complexity of network maintenance.

Description

Technical Field

[0001] This application relates to the field of network communication technology, and in particular to a cross-server communication method, apparatus, device and storage medium based on RSocket. Background Technology

[0002] In game design, game projects are typically deployed in a multi-server manner, with each server operating as an independent process and data isolated between servers. When server A needs to communicate with server B, server A needs to know server B's address, establish a connection with server B, and then begin communication. At this point, the network topology formed by the various servers is a mesh structure.

[0003] As the number of sub-servers increases, the number of connections between sub-servers will grow exponentially. If a game project has 1,000 sub-servers, then a total of approximately 1,000 * 1,000 connections need to be established. This communication method significantly increases resource consumption and also increases the complexity of network maintenance. Summary of the Invention

[0004] This application provides a cross-server communication method, apparatus, device, and storage medium based on RSocket. In game projects with many sub-servers, it significantly reduces the resource consumption of communication between sub-servers and reduces the complexity of network maintenance.

[0005] In a first aspect, embodiments of this application provide a cross-server communication method based on RSocket, the method comprising:

[0006] Receive a connection request sent by a first client, wherein the connection request records the node information of the first client, and the node information includes a role identifier and a node identifier;

[0007] The node information is added to the routing table, which records node information sent by multiple different first clients;

[0008] The system receives a request message sent by a second client, determines the target node corresponding to the request message based on the routing information recorded in the request message and the node information recorded in the routing table, and forwards the request message to the target node.

[0009] Optionally, adding the node information to the routing table includes:

[0010] After associating the role identifier and node identifier in the node information, the node identifier is added to the routing table. Each node identifier recorded in the routing table uniquely corresponds to a role identifier, and each role identifier corresponds to one or more node identifiers.

[0011] Optionally, the routing information includes a routing type and specified data. Determining the target node corresponding to the request message based on the routing information recorded in the request message and the node information recorded in the routing table includes:

[0012] The identifier of the node to be matched is determined based on the route type and specified data in the routing information.

[0013] Based on the identifier of the node to be matched, the node information recorded in the routing table is queried to determine the target node corresponding to the request message.

[0014] Optionally, the route type includes a node-specified type. Correspondingly, determining the identifier of the node to be matched based on the route type and specified data in the route information includes:

[0015] When the routing type is a node-specified type, the node identifier recorded in the specified data is determined as the node identifier to be matched.

[0016] Optionally, the node specification type includes a single node specification type and a full node specification type, and determining the node identifier recorded in the specified data as the node identifier to be matched includes:

[0017] When the node specified type is a single node specified type, the unique node identifier recorded in the specified data is determined as the node identifier to be matched;

[0018] When the node specified type is a full node specified type, all node identifiers recorded in the specified data are determined as node identifiers to be matched.

[0019] Optionally, the route type includes a role-specified type. Correspondingly, determining the identifier of the node to be matched based on the route type and specified data in the route information includes:

[0020] When the routing type is a role-specified type, the identifier of the node to be matched is determined based on the role identifier recorded in the specified data.

[0021] Optionally, the role specification type includes a single role specification type and a multi-role specification type. Correspondingly, determining the node identifier to be matched based on the role identifier recorded in the specified data includes:

[0022] When the role specification type is a single role specification type, the role identifier recorded in the specified data is used as the node identifier to be matched, and is used to determine any one or all of the corresponding nodes as the target node in the routing table based on the role identifier;

[0023] When the role specification type is a multi-role specification type, the multiple role identifiers recorded in the specified data are used as node identifiers to be matched, and all corresponding nodes in the routing table are determined as target nodes based on any one of the multiple role identifiers.

[0024] Secondly, embodiments of this application also provide a cross-server communication system based on RSocket, including:

[0025] The receiving module is used to receive a connection request sent by a first client. The connection request contains node information of the first client, including role identifier and node identifier.

[0026] An add module is used to add the node information to a routing table, which records node information sent by multiple different first clients;

[0027] The determination module is used to receive a request message sent by a second client and determine the target node corresponding to the request message based on the routing information recorded in the request message and the node information recorded in the routing table.

[0028] The forwarding module is used to forward the request message to the target node.

[0029] Thirdly, embodiments of this application also provide an electronic device, the device comprising:

[0030] One or more processors;

[0031] Storage device for storing one or more programs.

[0032] When the one or more programs are executed by the one or more processors, the one or more processors implement the cross-server communication method based on RSocket as described in the embodiments of this application.

[0033] Fourthly, embodiments of this application also provide a non-volatile storage medium for storing computer-executable instructions, which, when executed by a computer processor, are used to execute the cross-server communication method based on RSocket described in embodiments of this application.

[0034] Fifthly, embodiments of this application also provide a computer program product, which includes a computer program stored in a computer-readable storage medium. At least one processor of the device reads from the computer-readable storage medium and executes the computer program, causing the device to perform the cross-server communication method based on RSocket described in embodiments of this application.

[0035] In this embodiment, a connection request sent by a first client is received. This connection request contains node information of the first client, including a role identifier and a node identifier. This node information is added to a routing table, which records node information from multiple different first clients. A request message sent by a second client is received. Based on the routing information recorded in the request message and the node information recorded in the routing table, the target node corresponding to the request message is determined, and the request message is forwarded to the target node. This solution, by recording the node information of the client requesting the connection in the routing table (including a role identifier and a node identifier), and determining the target node corresponding to the request message from the client sending the request message, significantly reduces the resource consumption of communication between different sub-servers and reduces the complexity of network maintenance. Attached Figure Description

[0036] Figure 1 A flowchart illustrating a cross-server communication method based on RSocket, provided as an embodiment of this application;

[0037] Figure 2 A flowchart illustrating another cross-server communication method based on RSocket provided in this application embodiment;

[0038] Figure 3 A flowchart illustrating another cross-server communication method based on RSocket provided in this application embodiment;

[0039] Figure 4 A structural block diagram of a cross-server communication system based on RSocket provided in this application embodiment;

[0040] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0041] The embodiments of this application will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of the embodiments of this application and are not intended to limit the scope of the embodiments. Furthermore, it should be noted that, for ease of description, only the parts relevant to the embodiments of this application are shown in the accompanying drawings, not the entire structure.

[0042] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0043] The cross-server communication method based on RSocket provided in this application can be executed by computing devices such as desktop computers and servers. RSocket is short for Reactive Socket. RSocket is a language-independent network protocol located at layers 5 / 6 of the OSI seven-layer model or the application layer of the TCP / IP model. It is a bidirectional, multiplexed, message-based, reactive backpressure-based binary protocol.

[0044] Figure 1 A flowchart illustrating a cross-server communication method based on RSocket provided in this application embodiment is shown below. Figure 1 As shown, the specific steps include the following:

[0045] Step S101: Receive a connection request sent by the first client. The connection request contains node information of the first client, including role identifier and node identifier.

[0046] The first client is the client that sends connection requests to the proxy node. Each first client can correspond to a sub-server. In the current network topology, multiple proxy nodes can exist at the same time. In this embodiment, the processing of one proxy node is described.

[0047] In one embodiment, the connection request records node information of the first client, including a role identifier and a node identifier. The role identifier can be an identifier used to identify the function of the node, i.e., the first client; for example, different role identifiers correspond to game servers, combat servers, chat servers, etc. The node identifier can be the network ID of the first client. For each role identifier, one role identifier can correspond to one or more node identifiers. For example, the role identifier "game server" can correspond to multiple nodes, i.e., multiple different first clients. For each first client, as a node, it uniquely corresponds to one role identifier.

[0048] Step S102: Add the node information to the routing table, which records node information sent by multiple different first clients.

[0049] In one embodiment, the node information of the first client is added to a created routing table that records node information sent by multiple different first clients. Optionally, the role identifier and node identifier in the node information are associated before being added to the routing table.

[0050] Step S103: Receive a request message sent by the second client, determine the target node corresponding to the request message based on the routing information recorded in the request message and the node information recorded in the routing table, and forward the request message to the target node.

[0051] The second client is the client that requests to establish a connection with other clients. It sends a request message to the proxy node. After receiving the request message sent by the second client, the proxy node determines the target node corresponding to the request message based on the routing information recorded in the request message and the node information recorded in the routing table.

[0052] In one embodiment, the routing information recorded in the request message includes a routing type and specified data. Determining the target node corresponding to the request message based on the routing information recorded in the request message and the node information recorded in the routing table includes: determining the identifier of the node to be matched based on the routing type and specified data in the routing information; querying the node information recorded in the routing table based on the identifier of the node to be matched; and determining the target node corresponding to the request message. Specifically, the routing information recorded in the request message includes a routing type and specified data. When determining the target node corresponding to the request message, the identifier of the node to be matched is determined based on the routing type and specified data, and a query and matching is performed based on the recorded routing table to determine the target node corresponding to the request message.

[0053] As described above, the system receives connection requests from the first client, which contain node information including a role identifier and a node identifier. This node information is added to the routing table, which records node information from multiple different first clients. The system also receives request messages from the second client, determines the target node corresponding to the request message based on the routing information recorded in the request message and the node information recorded in the routing table, and forwards the request message to the target node. This solution significantly reduces resource consumption in communication between different sub-servers and lowers the complexity of network maintenance by recording the node information of the client requesting the connection (including a role identifier and a node identifier) ​​in the routing table and determining the target node corresponding to the request message from the client sending the request message.

[0054] Figure 2 A flowchart of another cross-server communication method based on RSocket provided in the embodiments of this application is shown below. Figure 2 As shown, a specific method for determining the target node of a request message is given, including:

[0055] Step S201: Receive a connection request sent by the first client. The connection request contains node information of the first client, including role identifier and node identifier.

[0056] Step S202: Add the node information to the routing table, which records node information sent by multiple different first clients.

[0057] Step S203: Receive a request message sent by the second client. The routing information recorded in the request message includes the routing type and specified data.

[0058] Step S204: When the routing type is a node specified type, the node identifier recorded in the specified data is determined as the node identifier to be matched, and the node information recorded in the routing table is queried based on the node identifier to be matched to determine the target node corresponding to the request message.

[0059] In one embodiment, the routing type can be divided into node-specified type and role-specified type. In the case of node-specified type, the node identifier recorded in the specified data is determined as the node identifier to be matched. Optionally, the node-specified type can be further divided into single-node-specified type and full-node-specified type. Optionally, the node identifier to be matched can be determined as follows: in the case of single-node-specified type, the unique node identifier recorded in the specified data is determined as the node identifier to be matched; in the case of full-node-specified type, all node identifiers recorded in the specified data are determined as the node identifiers to be matched. Specifically, for single-node-specified type, the specified data can be a specific node identifier, which is used as the node identifier to be matched; for full-node-specified type, the specified data can be multiple node identifiers, in which case all multiple node identifiers are determined as the node identifiers to be matched. At this time, the corresponding routing table is queried to see if the node identifier corresponding to the node identifier to be matched is recorded. If it exists, the node corresponding to the matched node identifier is taken as the target node, and the request message is forwarded to the target node.

[0060] As described above, by receiving connection requests from the first client, which contain node information including a role identifier and a node identifier, and adding this node information to the routing table (which records node information from multiple different first clients), and receiving request messages from the second client, the target node corresponding to the request message is determined based on the routing information recorded in the request message and the node information recorded in the routing table. The request message is then forwarded to the target node. In this scheme, by recording the node information of the client requesting the connection in the routing table (including a role identifier and a node identifier), and determining the target node corresponding to the request message from the client sending the request message, the resource consumption for communication between different sub-servers is significantly reduced, and the complexity of network maintenance is lowered.

[0061] Figure 3 A flowchart of another cross-server communication method based on RSocket provided in the embodiments of this application is shown below. Figure 3 As shown, another specific method for determining the target node of a request message is given, including:

[0062] Step S301: Receive a connection request sent by the first client. The connection request contains node information of the first client, including role identifier and node identifier.

[0063] Step S302: Add the node information to the routing table, which records node information sent by multiple different first clients.

[0064] Step S303: Receive a request message sent by the second client. The routing information recorded in the request message includes the routing type and specified data.

[0065] Step S304: If the routing type is a role-specified type, determine the identifier of the node to be matched based on the role identifier recorded in the specified data, query the node information recorded in the routing table based on the identifier of the node to be matched, and determine the target node corresponding to the request message.

[0066] In one embodiment, when the routing type is role-specified, the identifier of the node to be matched is determined based on the role identifier recorded in the specified data. Then, the node information recorded in the routing table is queried based on the node identifier to be matched to determine the target node corresponding to the request message. Optionally, the role-specified type includes single-role-specified type and multi-role-specified type.

[0067] An exemplary determination method could be as follows: When the role specification type is a single role specification type, the role identifier recorded in the specified data is used as the node identifier to be matched, and this is used to determine any one or all corresponding nodes as the target node in the routing table based on the role identifier. When the role specification type is a multi-role specification type, multiple role identifiers recorded in the specified data are used as node identifiers to be matched, and this is used to determine all corresponding nodes as the target node in the routing table based on any one of the multiple role identifiers. Specifically, for the single role specification type, the role identifier in the specified data is used as the node identifier to be matched to query the routing table, and the nodes corresponding to one or all node identifiers of the same role identifier are determined as the target nodes. The specific decision of whether to select one target node or all target nodes can be determined based on the information recorded in the request message. For example, if a specific field in the request message or a setting bit in the request frame indicates that a target node is selected, then any one target node is determined. If the record indicates that all target nodes are selected, then the nodes corresponding to all node identifiers of that role identifier are determined as the target nodes.

[0068] In cases where multiple roles are specified, the multiple role identifiers recorded in the specified data are used together as the node identifiers to be matched. In this case, the routing table is queried, and any one role identifier is selected from the multiple role identifiers. The node corresponding to all node identifiers of the selected role identifier is determined in the routing table as the target node.

[0069] As described above, by receiving connection requests from the first client, which contain node information including a role identifier and a node identifier, and adding this node information to the routing table (which records node information from multiple different first clients), and receiving request messages from the second client, the target node corresponding to the request message is determined based on the routing information recorded in the request message and the node information recorded in the routing table. The request message is then forwarded to the target node. In this scheme, by recording the node information of the client requesting the connection in the routing table (including a role identifier and a node identifier), and determining the target node corresponding to the request message from the client sending the request message, the resource consumption for communication between different sub-servers is significantly reduced, and the complexity of network maintenance is lowered.

[0070] Figure 4 A structural block diagram of a cross-server communication device based on RSocket provided in this application embodiment is shown below. Figure 4 As shown, this device is used to execute the cross-server communication method based on RSocket provided in the above embodiments, and has the corresponding functional modules and beneficial effects for executing the method. Figure 4As shown, the device specifically includes: a receiving module 101, an adding module 102, a determining module 103, and a forwarding module 104, wherein,

[0071] The receiving module 101 is used to receive a connection request sent by a first client. The connection request records the node information of the first client, and the node information includes a role identifier and a node identifier.

[0072] The addition module 102 is used to add the node information to the routing table, which records node information sent by multiple different first clients;

[0073] The determination module 103 is used to receive a request message sent by the second client and determine the target node corresponding to the request message based on the routing information recorded in the request message and the node information recorded in the routing table.

[0074] The forwarding module 104 is used to forward the request message to the target node.

[0075] As described above, by receiving connection requests from the first client, which contain node information including a role identifier and a node identifier, and adding this node information to the routing table (which records node information from multiple different first clients), and receiving request messages from the second client, the target node corresponding to the request message is determined based on the routing information recorded in the request message and the node information recorded in the routing table. The request message is then forwarded to the target node. In this scheme, by recording the node information of the client requesting the connection in the routing table (including a role identifier and a node identifier), and determining the target node corresponding to the request message from the client sending the request message, the resource consumption for communication between different sub-servers is significantly reduced, and the complexity of network maintenance is lowered.

[0076] In one possible embodiment, adding the node information to the routing table includes:

[0077] After associating the role identifier and node identifier in the node information, the node identifier is added to the routing table. Each node identifier recorded in the routing table uniquely corresponds to a role identifier, and each role identifier corresponds to one or more node identifiers.

[0078] In one possible embodiment, the routing information includes a routing type and specified data, and the determining module 103 is specifically used for:

[0079] The identifier of the node to be matched is determined based on the route type and specified data in the routing information.

[0080] Based on the identifier of the node to be matched, the node information recorded in the routing table is queried to determine the target node corresponding to the request message.

[0081] In one possible embodiment, the routing type includes a node-specified type, and the determining module 103 is specifically used for:

[0082] When the routing type is a node-specified type, the node identifier recorded in the specified data is determined as the node identifier to be matched.

[0083] In one possible embodiment, the node specification type includes a single node specification type and a full node specification type, and the determining module 103 is specifically used for:

[0084] When the node specified type is a single node specified type, the unique node identifier recorded in the specified data is determined as the node identifier to be matched;

[0085] When the node specified type is a full node specified type, all node identifiers recorded in the specified data are determined as node identifiers to be matched.

[0086] In one possible embodiment, the routing type includes a role-assigned type, and the determining module 103 is specifically used for:

[0087] When the routing type is a role-specified type, the identifier of the node to be matched is determined based on the role identifier recorded in the specified data.

[0088] In one possible embodiment, the role assignment type includes a single role assignment type and a multi-role assignment type, and the determining module 103 is specifically used for:

[0089] When the role specification type is a single role specification type, the role identifier recorded in the specified data is used as the node identifier to be matched, and is used to determine any one or all of the corresponding nodes as the target node in the routing table based on the role identifier;

[0090] When the role specification type is a multi-role specification type, the multiple role identifiers recorded in the specified data are used as node identifiers to be matched, and all corresponding nodes in the routing table are determined as target nodes based on any one of the multiple role identifiers.

[0091] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application, such as... Figure 5 As shown, the device includes a processor 201, a memory 202, an input device 203, and an output device 204; the number of processors 201 in the device can be one or more. Figure 5Taking a processor 201 as an example; the processor 201, memory 202, input device 203, and output device 204 in the device can be connected via a bus or other means. Figure 5 Taking a bus connection as an example, the memory 202, as a computer-readable storage medium, can be used to store software programs, computer-executable programs, and modules, such as the program instructions / modules corresponding to the cross-server communication method based on RSocket in this embodiment. The processor 201 executes various functional applications and data processing of the device by running the software programs, instructions, and modules stored in the memory 202, thereby implementing the aforementioned cross-server communication method based on RSocket. The input device 703 can be used to receive input digital or character information and generate key signal inputs related to user settings and function control of the device. The output device 204 may include a display screen or other display device.

[0092] This application also provides a non-volatile storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to perform a cross-server communication method based on RSocket described in the above embodiments, wherein the method includes:

[0093] Receive a connection request sent by a first client, wherein the connection request records the node information of the first client, and the node information includes a role identifier and a node identifier;

[0094] The node information is added to the routing table, which records node information sent by multiple different first clients;

[0095] The system receives a request message sent by a second client, determines the target node corresponding to the request message based on the routing information recorded in the request message and the node information recorded in the routing table, and forwards the request message to the target node.

[0096] It is worth noting that in the above embodiments of the cross-server communication system based on RSocket, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the protection scope of the embodiments of this application.

[0097] In some possible implementations, various aspects of the methods provided in this application can also be implemented as a program product comprising program code that, when run on a computer device, causes the computer device to perform the steps of the methods according to the various exemplary embodiments of this application described above. For example, the computer device can execute the cross-server communication method based on RSocket as described in the embodiments of this application. The program product can be implemented using any combination of one or more readable media.

Claims

1. A cross-server communication method based on RSocket, applied to proxy nodes, characterized in that, include: Receive a connection request sent by a first client, wherein the connection request records the node information of the first client, and the node information includes a role identifier and a node identifier; The node information is added to the routing table, which records node information sent by multiple different first clients. Each first client corresponds to a sub-server, and the data between different sub-servers is isolated from each other. The system receives a request message from a second client, determines the identifier of the node to be matched based on the routing type and specified data in the routing information recorded in the request message, queries the node information recorded in the routing table based on the identifier of the node to be matched, determines the target node corresponding to the request message, and forwards the request message to the target node. The routing type includes node-specified type and role-specified type. Determining the identifier of the node to be matched based on the routing type and specified data in the request message includes: when the role-specified type is a single-role-specified type, using the role identifier recorded in the specified data as the identifier of the node to be matched, for determining any one or all corresponding nodes as target nodes in the routing table based on the role identifier; when the role-specified type is a multi-role-specified type, using multiple role identifiers recorded in the specified data as identifiers of the node to be matched, for determining all corresponding nodes as target nodes in the routing table based on any one of the multiple role identifiers.

2. The cross-server communication method based on RSocket according to claim 1, characterized in that, Adding the node information to the routing table includes: After associating the role identifier and node identifier in the node information, the node identifier is added to the routing table. Each node identifier recorded in the routing table uniquely corresponds to a role identifier, and each role identifier corresponds to one or more node identifiers.

3. The cross-server communication method based on RSocket according to claim 1, characterized in that, The step of determining the identifier of the node to be matched based on the route type and specified data in the routing information includes: When the routing type is a node-specified type, the node identifier recorded in the specified data is determined as the node identifier to be matched.

4. The cross-server communication method based on RSocket according to claim 3, characterized in that, The node specification type includes single node specification type and full node specification type, and the step of determining the node identifier recorded in the specified data as the node identifier to be matched includes: When the node specified type is a single node specified type, the unique node identifier recorded in the specified data is determined as the node identifier to be matched; When the node specified type is a full node specified type, all node identifiers recorded in the specified data are determined as node identifiers to be matched.

5. A cross-server communication device based on RSocket, characterized in that, include: The receiving module is used to receive a connection request sent by a first client. The connection request contains node information of the first client, including role identifier and node identifier. An add module is used to add the node information to the routing table. The routing table records node information sent by multiple different first clients. Each first client corresponds to a sub-server, and the data between different sub-servers is isolated from each other. The determination module is used to receive a request message sent by a second client, determine the identifier of the node to be matched based on the routing type and specified data in the routing information recorded in the request message, query the node information recorded in the routing table based on the identifier of the node to be matched, and determine the target node corresponding to the request message. The routing type includes a node-specified type and a role-specified type. Specifically, the determination module is used to: when the role-specified type is a single-role-specified type, use the role identifier recorded in the specified data as the identifier of the node to be matched, and determine any one or all corresponding nodes as the target node based on the role identifier in the routing table; when the role-specified type is a multi-role-specified type, use multiple role identifiers recorded in the specified data as the identifiers of the node to be matched, and determine all corresponding nodes as the target node based on any one of the multiple role identifiers in the routing table. The forwarding module is used to forward the request message to the target node.

6. An electronic device, the device comprising: One or more processors; A storage device for storing one or more programs, which, when executed by one or more processors, enable the one or more processors to implement the cross-server communication method based on RSocket as described in any one of claims 1-4.

7. A non-volatile storage medium for storing computer-executable instructions, which, when executed by a computer processor, are used to perform the cross-server communication method based on RSocket as described in any one of claims 1-4.

Images