CN112187816B - RPC request processing method, equipment and storage medium - Google Patents
RPC request processing method, equipment and storage medium Download PDFInfo
- Publication number
- CN112187816B CN112187816B CN202011069806.8A CN202011069806A CN112187816B CN 112187816 B CN112187816 B CN 112187816B CN 202011069806 A CN202011069806 A CN 202011069806A CN 112187816 B CN112187816 B CN 112187816B
- Authority
- CN
- China
- Prior art keywords
- node
- rpc
- request information
- service
- sending
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/133—Protocols for remote procedure calls [RPC]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer And Data Communications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides an RPC request processing method, equipment and a storage medium, wherein the method comprises the following steps: receiving node registration request information, and storing the service address of the first node into a node list of a corresponding main chain or parallel chain; the first node generates and sends the node registration request information according to the name and the service address of the block chain to which the first node belongs; receiving RPC service request information sent by a first user terminal, analyzing the RPC service request information to obtain a first block chain name and generating a first RPC request; searching a corresponding first node list according to the first block chain name and selecting a node; sending a first RPC request to the service address of the selected node, and monitoring whether the sending is successful: if not, selecting one node from the first node list and returning; if yes, the sending result is returned to the first user end. The invention can ensure the availability and stability of RPC service externally provided by the block chain node without the need of maintaining a large number of service addresses of the node by the user side.
Description
Technical Field
The present application relates to the field of block chain technology, and in particular, to a method, device, and storage medium for processing an RPC request.
Background
Currently, when a user side sends a data query request or sends an RPC request such as a transaction to a block chain, the data query request or the RPC request is directly sent to a block chain node. The user side needs to maintain the addresses and ports of a plurality of nodes in the block chain locally, so that when the RPC request needs to be sent, the RPC request is sent to the block chain nodes according to the addresses and the ports of the nodes maintained locally.
The problem of the above scheme is that as the number of parallel chains increases, the number of parallel chain link point addresses and ports that the user terminal needs to maintain also increases greatly, so that the user terminal can only maintain a small number of node addresses and ports for one parallel chain (or main chain); meanwhile, the deployment and service stability of the blockchain nodes are far less than that of the centralized server, and when each node of a certain parallel chain (or main chain) maintained by the user terminal happens to modify a deployed address or port, is down or is down, the user terminal cannot access the service of the blockchain.
Disclosure of Invention
In view of the above-mentioned defects or shortcomings in the prior art, it is desirable to provide an RPC request processing method, device and storage medium that can ensure availability and stability of an RPC service externally provided by a block chain node without a user side maintaining a large number of service addresses of the node.
In a first aspect, the present invention provides a RPC request processing method applicable to an RPC server, including:
receiving node registration request information, and storing the service address of the first node into a node list of a corresponding main chain or a parallel chain according to the node registration request information; the first node generates and sends the node registration request information according to the name and the service address of the block chain to which the first node belongs;
receiving RPC service request information sent by a first user end, analyzing the RPC service request information to obtain a first block chain name and generate a first RPC request;
searching a corresponding first node list according to the first block chain name and selecting a node from the first node list;
sending a first RPC request to the service address of the selected node, and monitoring whether the sending is successful:
if not, selecting one node from the first node list alternatively, and returning to send the first RPC request to the service address of the selected node;
if yes, the sending result is returned to the first user terminal.
In a second aspect, the present invention provides a RPC request processing method applicable to a block chain node, including:
generating node registration request information according to the name of a block chain to which the current node belongs and the service address of the current node, and sending the node registration request information to a first RPC server so that the first RPC server can store the service address into a node list of a corresponding main chain or a parallel chain;
Receiving and responding to a first RPC request sent by a first RPC server, so that the first RPC server returns a sending result to the first user side;
the first RPC server receives RPC service request information sent by a first user end, analyzes the generated RPC service request information and obtains a first block chain name; the first RPC server searches a corresponding first node list according to the first block chain name, selects the first node list from the first node list and sends the first RPC request to the current node; the first RPC server is also used for reselecting nodes from the first node list and sending the first RPC request when the first RPC request is unsuccessfully sent.
In a third aspect, the present invention further provides a method for processing an RPC request applicable to a user side, including:
generating RPC service request information and sending the RPC service request information to a first RPC server for the first RPC server to:
analyzing the RPC service request information to obtain a first block chain name and generate a first RPC request;
searching a corresponding first node list according to the first block chain name and selecting a node from the first node list;
sending a first RPC request to the service address of the selected node, and monitoring whether the sending is successful:
if not, selecting one node from the first node list alternatively, and returning to send the first RPC request to the service address of the selected node;
If yes, returning the sending result to the current user side;
and receiving a sending result returned by the first RPC server.
In a fourth aspect, the present invention also provides an apparatus comprising one or more processors and a memory, wherein the memory contains instructions executable by the one or more processors to cause the one or more processors to perform the RPC request processing method provided according to embodiments of the present invention.
In a fifth aspect, the present invention also provides a storage medium storing a computer program that causes a computer to execute the RPC request processing method provided according to the embodiments of the present invention.
According to the RPC request processing method, the RPC request processing equipment and the RPC server, provided by the embodiments of the invention, the RPC server is deployed and maintains a large number of service addresses of the main chain nodes and the parallel chain nodes, the RPC request is forwarded to the block chain nodes for the user side, and another node of the same block chain is switched to be retransmitted when the transmission fails, so that the RPC request of the user side can be ensured to be transmitted to the corresponding block chain network, and the availability and the stability of the RPC service externally provided by the block chain nodes can be ensured without the user side maintaining the service addresses of a large number of nodes.
Drawings
Other features, objects and advantages of the present application will become more apparent upon reading of the following detailed description of non-limiting embodiments thereof, made with reference to the accompanying drawings in which:
fig. 1 is a flowchart of a method for processing an RPC request according to an embodiment of the present invention.
Fig. 2 is a flowchart of another RPC request processing method according to an embodiment of the present invention.
Fig. 3 is a flowchart of another RPC request processing method according to an embodiment of the present invention.
Fig. 4 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
Detailed Description
The present application will be described in further detail with reference to the following drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the relevant invention and not restrictive of the invention. It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings.
It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict. The present application will be described in detail below with reference to the embodiments with reference to the attached drawings.
Fig. 1 is a flowchart of a method for processing an RPC request according to an embodiment of the present invention.
As shown in fig. 1, in this embodiment, the present invention provides an RPC request processing method suitable for an RPC server, including:
s11: receiving node registration request information, and storing the service address of the first node into a node list of a corresponding main chain or a parallel chain according to the node registration request information; the first node generates and sends the node registration request information according to the name and the service address of the block chain to which the first node belongs;
s12: receiving RPC service request information sent by a first user terminal, analyzing the RPC service request information to obtain a first block chain name and generating a first RPC request;
s13: searching a corresponding first node list according to the first block chain name and selecting a node from the first node list;
s14: sending a first RPC request to the service address of the selected node, and monitoring whether the sending is successful:
otherwise, step S15 is executed: selecting one node from the first node list, and returning to step S14;
if yes, go to step S16: and returning the sending result to the first user terminal.
Specifically, the following parallel chains a are arranged in the main chain A1-a10The main chain B is provided with a parallel chain B1-b16The main chain C is provided with a parallel chain C1-c22… …, the main chain H has no parallel chain, the client x sends RPC request to the block chain node directly, the client y sends RPC request to the block chain node through RPC server z (according to the method shown in FIG. 1) as an example, the method is exemplarily explained as follows:
For the user terminal x, in case of hundreds of total main chains and parallel chains, if each chain maintains 3-5 node addresses and ports, the user terminal x needs to maintain hundreds of node addresses and ports, it is difficult for the user terminal x to bear such many addresses and ports, and even if it can be maintained, it is difficult to guarantee 100% success in accessing the required RPC service when it is needed.
For the user end y, compared with the user end x, the user end y does not need to locally maintain the addresses and ports of all the main chain nodes and the parallel chain nodes, and only needs to use the service of the RPC server z.
In this embodiment, after the address and the port of the RPC service are deployed or modified, each main chain node and each parallel chain node generate node registration request information according to the name of the block chain to which the current node belongs and the service address of the current node, and send the node registration request information to the RPC server z. For example, parallel chains a3Node a of3-7After modifying the port of the RPC service, according to the name a of the block chain to which the node belongs3And the service address IP after the node modifies the port1:Port1Generating node registration request informationm1M is1And sending to the RPC server z. In other embodiments, each main chain node and each parallel chain node may be further configured to generate and send node registration request information under different conditions, for example, receiving a query message sent by an RPC server, or receiving an instruction of a node controller, and so on.
In step S11, the RPC server z receives the node registration request information sent by each main chain node and each parallel chain node, and updates the locally stored node list of the corresponding main chain or parallel chain according to the received node registration request information. Receiving node registration request message m by RPC server z1For example, node a3-7Service address of (IP)1:Port1In parallel chains a3A list of nodes.
When the user end y needs to inquire the parallel chain a3When the data is in progress, the user end y is according to the name a of the target block chain3The type of RPC request (data query), the transaction tx queried1Transaction hash of (tx)1) Equal information generation RPC service request information q1Q is mixing q1And sending to the RPC server z.
In step S12, RPC server z receives q1To q is paired1Analyzing to obtain the name a of the block chain3Request type (data query), hash (tx)1) Waiting for information according to request type (data query), hash (tx)1) Wait for information generation according to hash (tx)1) Inquiry RPC request r1。
In step S13, RPC server z follows the block chain name a3Find out the locally maintained parallel chain a3And selects a node a from the node list3-5. Specifically, the node selection manner may be configured to select a first node in the list, or a node that has been successfully accessed last time, and the like in any manner commonly used in the art.
In step S14, the RPC server z directs the node a selected in step S133-5Service address of (IP)2:Port2Transmitting the RPC request r generated in step S121And monitoring whether or not to send outSuccess is sent:
otherwise, go to step S15 to get parallel chain a3Is alternatively selected from a node a3-11Returning to step S14, the node a is connected3-11Service address of (IP)3:Port3Sending r1And monitoring whether the transmission is successful:
if yes, step S16 is executed to return the sending result to the user end y.
The above embodiment takes an example that the user terminal y sends an RPC request of a data query type to the block link node through the RPC server z, and exemplarily explains the method in fig. 1. In further embodiments, the RPC request may also be configured to send a transaction or other types, the number of RPC servers may be configured to be multiple, and the user side may optionally send RPC service request information from one of the multiple RPC servers, which may achieve the same technical effect.
Preferably, before the selecting a node from the first node list, the method further includes: and moving the node which fails to send to the end of the first node list.
In the embodiment, the RPC server for maintaining the service addresses of a large number of main chain nodes and parallel chain nodes is deployed, the RPC server forwards the RPC request to the block chain nodes for the user side, and switches another node of the same block chain to resend the RPC request when the RPC request fails to be sent, so that the RPC request of the user side can be sent to the corresponding block chain network, and the availability and the stability of the RPC service externally provided by the block chain nodes can be guaranteed without the user side maintaining the service addresses of a large number of nodes.
Fig. 2 is a flowchart of another RPC request processing method according to an embodiment of the present invention. The method illustrated in fig. 2 may be performed in conjunction with the method illustrated in fig. 1.
As shown in fig. 2, in this embodiment, the present invention further provides an RPC request processing method suitable for a block chain node, including:
s21: generating node registration request information according to the name of a block chain to which the current node belongs and the service address of the current node, and sending the node registration request information to a first RPC server so that the first RPC server can store the service address into a node list of a corresponding main chain or a parallel chain;
s23: and receiving and responding to the first RPC request sent by the first RPC server, so that the first RPC server returns a sending result to the first user terminal.
The first RPC server receives RPC service request information sent by the first user terminal, analyzes the RPC service request information and generates and obtains a first block chain name; the first RPC server searches a corresponding first node list according to the first block chain name, selects the first node list from the first node list and sends the first node list to a current node; the first RPC server is also used for reselecting the node from the first node list and sending the first RPC request when the first RPC request is failed to be sent.
The RPC request processing principle of the method shown in fig. 2 can refer to the method shown in fig. 1, and is not described herein again.
Fig. 3 is a flowchart of another RPC request processing method according to an embodiment of the present invention. The method illustrated in fig. 3 may be performed in conjunction with the methods illustrated in fig. 1-2.
As shown in fig. 3, in this embodiment, the present invention further provides a method for processing an RPC request applicable to a user side, including:
s31: generating RPC service request information and sending to a first RPC server for the first RPC server:
analyzing the RPC service request information to obtain a first block chain name and generate a first RPC request;
searching a corresponding first node list according to the first block chain name and selecting a node from the first node list;
sending a first RPC request to the service address of the selected node, and monitoring whether the sending is successful:
if not, selecting one node from the first node list alternatively, and returning to send the first RPC request to the service address of the selected node;
if yes, returning the sending result to the current user side;
s33: and receiving a sending result returned by the first RPC server.
Preferably, the generating RPC service request information includes: and generating RPC service request information according to the name of the target block chain, the RPC request type, the request content or the parameters.
In another preferred embodiment, the user side can also directly generate an RPC request, and the name of the target block chain and the RPC request are packaged to generate RPC service request information; when the RPC server analyzes the RPC service request information, the RPC request can be directly obtained.
The RPC request processing principle of the method shown in fig. 3 can also refer to the method shown in fig. 1, and is not described herein again.
Fig. 4 is a schematic structural diagram of an apparatus according to an embodiment of the present invention.
As shown in fig. 4, as another aspect, the present application also provides a device 400 including one or more Central Processing Units (CPUs) 401 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)402 or a program loaded from a storage section 408 into a Random Access Memory (RAM) 403. In the RAM403, various programs and data necessary for the operation of the device 400 are also stored. The CPU401, ROM402, and RAM403 are connected to each other via a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.
The following components are connected to the I/O interface 405: an input section 406 including a keyboard, a mouse, and the like; an output section 407 including a display device such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage section 408 including a hard disk and the like; and a communication section 409 including a network interface card such as a LAN card, a modem, or the like. The communication section 409 performs communication processing via a network such as the internet. A driver 410 is also connected to the I/O interface 405 as needed. A removable medium 411 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 410 as necessary, so that a computer program read out therefrom is mounted into the storage section 408 as necessary.
In particular, according to an embodiment of the present disclosure, the method described in any of the above embodiments may be implemented as a computer software program. For example, embodiments of the present disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program comprising program code for performing any of the methods described above. In such an embodiment, the computer program may be downloaded and installed from a network through the communication section 409, and/or installed from the removable medium 411.
As yet another aspect, the present application also provides a computer-readable storage medium, which may be the computer-readable storage medium included in the apparatus of the above-described embodiment; or it may be a separate computer readable storage medium not incorporated into the device. The computer readable storage medium stores one or more programs for use by one or more processors in performing the methods described in the present application.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units or modules described in the embodiments of the present application may be implemented by software or hardware. The described units or modules may also be provided in a processor, for example, each unit may be a software program provided in a computer or a mobile intelligent device, or may be a separately configured hardware device. Wherein the designation of such a unit or module does not in some way constitute a limitation on the unit or module itself.
The foregoing description is only exemplary of the preferred embodiments of the application and is illustrative of the principles of the technology employed. It will be appreciated by those skilled in the art that the scope of the invention herein disclosed is not limited to the particular combination of features described above, but also encompasses other arrangements formed by any combination of the above features or their equivalents without departing from the spirit of the present application. For example, the above features may be replaced with (but not limited to) features having similar functions disclosed in the present application.
Claims (7)
1. An RPC request processing method, wherein the method is applied to an RPC server, and the method includes:
Receiving node registration request information, and storing a service address of a first node into a node list of a corresponding main chain or a parallel chain according to the node registration request information; the first node generates and sends the node registration request information according to the name of the block chain to which the first node belongs and the service address;
receiving RPC service request information sent by a first user end, analyzing the RPC service request information to obtain a first block chain name and generate a first RPC request;
searching a corresponding first node list according to the first block chain name and selecting a node from the first node list;
sending the first RPC request to the service address of the selected node, and monitoring whether the sending is successful:
if not, selecting one node from the first node list alternatively, and returning to the previous step: the first RPC request is sent to the service address of the selected node, and whether the sending is successful or not is monitored;
if yes, returning the sending result to the first user end.
2. The method of claim 1, wherein said selecting an alternative node from the first list of nodes further comprises:
and moving the node which fails to send to the end of the first node list.
3. An RPC request processing method, wherein the method is applied to a blockchain node, and the method comprises:
generating node registration request information according to the name of a block chain to which a current node belongs and the service address of the current node and sending the node registration request information to a first RPC server so that the first RPC server can store the service address into a node list of a corresponding main chain or a parallel chain;
receiving and responding to a first RPC request sent by the first RPC server, so that the first RPC server returns a sending result to the first user end;
the first RPC server receives RPC service request information sent by the first user terminal, and analyzes the generated RPC service request information and obtains a first block chain name; the first RPC server searches a corresponding first node list according to the first block chain name, selects the first node list from the first node list and sends the first node list to a current node; the first RPC server is also used for reselecting nodes from the first node list and sending the first RPC request when the first RPC request is sent unsuccessfully.
4. The RPC request processing method is characterized in that node registration request information is generated and sent to an RPC server by a first node according to the name and the service address of a block chain to which the first node belongs, the node registration request information is used for the RPC server to store the service address of the first node into a node list of a corresponding main chain or a parallel chain, the method is suitable for a user side, and the method comprises the following steps:
Generating RPC service request information and sending the RPC service request information to a first RPC server, so that the first RPC server:
analyzing the RPC service request information to obtain a first block chain name and generate a first RPC request;
searching a corresponding first node list according to the first block chain name and selecting a node from the first node list;
sending the first RPC request to the service address of the selected node, and monitoring whether the sending is successful:
if not, selecting one node from the first node list alternatively, and returning to the previous step: the first RPC request is sent to the service address of the selected node, and whether the sending is successful or not is monitored;
if yes, returning the sending result to the current user side;
and receiving the sending result returned by the first RPC server.
5. The method of claim 4, wherein generating the RPC service request message comprises:
and generating RPC service request information according to the name of the target block chain, the RPC request type, the request content or the parameters.
6. A computer device, the device comprising:
one or more processors;
a memory for storing one or more programs,
The one or more programs, when executed by the one or more processors, cause the one or more processors to perform the method recited in any of claims 1-5.
7. A storage medium storing a computer program, characterized in that the program, when executed by a processor, implements the method according to any one of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011069806.8A CN112187816B (en) | 2020-09-30 | 2020-09-30 | RPC request processing method, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011069806.8A CN112187816B (en) | 2020-09-30 | 2020-09-30 | RPC request processing method, equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112187816A CN112187816A (en) | 2021-01-05 |
| CN112187816B true CN112187816B (en) | 2022-06-28 |
Family
ID=73948575
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011069806.8A Active CN112187816B (en) | 2020-09-30 | 2020-09-30 | RPC request processing method, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112187816B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110557384A (en) * | 2019-08-12 | 2019-12-10 | 杭州云象网络技术有限公司 | internet of things management control method based on block chain |
| CN110851466A (en) * | 2020-01-16 | 2020-02-28 | 台州市相闻信息技术有限公司 | Visualization method and device for block chain system |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100512526C (en) * | 2004-11-26 | 2009-07-08 | 中国移动通信集团公司 | Method and system for proxy re-orienting terminal request |
| CN102546712B (en) * | 2010-12-20 | 2015-04-22 | 中国移动通信集团公司 | Message transmission method, equipment and system based on distributed service network |
| CN105915945A (en) * | 2015-12-08 | 2016-08-31 | 乐视云计算有限公司 | Content distribution method used for CDN platform and scheduling proxy server thereof |
| CN106357644B (en) * | 2016-09-21 | 2019-07-12 | 江苏通付盾科技有限公司 | Identity identifying method, system and server based on block chain network |
| CN107171794B (en) * | 2017-06-27 | 2019-10-22 | 葛峰 | A kind of electronic document signature method based on block chain and intelligent contract |
| CN110035097A (en) * | 2018-01-12 | 2019-07-19 | 广州中国科学院计算机网络信息中心 | Block chain identifies the isomery identification analytic method and system combined with Internet of Things |
| CN108667934A (en) * | 2018-05-11 | 2018-10-16 | 中国平安人寿保险股份有限公司 | Information processing method, device, electronic equipment and storage medium |
| CN108737418B (en) * | 2018-05-22 | 2020-09-15 | 飞天诚信科技股份有限公司 | Identity authentication method and system based on block chain |
| CN108833178B (en) * | 2018-06-22 | 2019-08-27 | 北京格瑞空间科技有限公司 | The internet of things equipment control method that a kind of block chain and central server combine |
| CN109033475B (en) * | 2018-09-10 | 2020-10-23 | 湖南智慧政务区块链科技有限公司 | File storage method, device, equipment and storage medium |
| CN109831313B (en) * | 2019-03-19 | 2021-02-26 | 全链通有限公司 | Group communication method, apparatus and computer-readable storage medium |
| CN110149323B (en) * | 2019-05-06 | 2020-07-10 | 山东公链信息科技有限公司 | Processing device with ten-million-level TPS (platform secure protocol) contract processing capacity |
| CN110443928A (en) * | 2019-08-19 | 2019-11-12 | 杭州宇链科技有限公司 | A kind of half centralization door-locking system based on block chain |
| CN110753105B (en) * | 2019-10-17 | 2022-09-06 | 中国建设银行股份有限公司 | Data transmission method, device, system, electronic equipment and storage medium |
-
2020
- 2020-09-30 CN CN202011069806.8A patent/CN112187816B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110557384A (en) * | 2019-08-12 | 2019-12-10 | 杭州云象网络技术有限公司 | internet of things management control method based on block chain |
| CN110851466A (en) * | 2020-01-16 | 2020-02-28 | 台州市相闻信息技术有限公司 | Visualization method and device for block chain system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112187816A (en) | 2021-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110417842B (en) | Fault processing method and device for gateway server | |
| US7987266B2 (en) | Failover in proxy server networks | |
| US6226684B1 (en) | Method and apparatus for reestablishing network connections in a multi-router network | |
| US8583810B2 (en) | Session affinity cache and manager | |
| CN109474936B (en) | Internet of things communication method and system applied among multiple lora gateways | |
| AU2012304550B2 (en) | SMB2 scaleout | |
| US20070150602A1 (en) | Distributed and Replicated Sessions on Computing Grids | |
| US10075549B2 (en) | Optimizer module in high load client/server systems | |
| US20070094361A1 (en) | Multipath routing process | |
| US8214506B2 (en) | Providing content to client device | |
| US8694580B2 (en) | Information processing apparatus, server selecting method and recording medium | |
| CN111352716B (en) | Task request method, device and system based on big data and storage medium | |
| US20110161961A1 (en) | Method and apparatus for optimized information transmission using dedicated threads | |
| CN109600380B (en) | Data transmission method and device | |
| US9350606B2 (en) | System and method for assigning server to terminal and efficiently delivering messages to the terminal | |
| CN111193789A (en) | Subscription information pushing method and device, computer equipment and readable storage medium | |
| US7457824B1 (en) | Methods and apparatus for managing groups of resources | |
| US20240171653A1 (en) | Network nodes and methods therein for indirect communication | |
| US20230254381A1 (en) | Service Request Handling | |
| CN112187816B (en) | RPC request processing method, equipment and storage medium | |
| US10904327B2 (en) | Method, electronic device and computer program product for searching for node | |
| US10819775B2 (en) | Systems and methods for server failover and load balancing | |
| CN111600929A (en) | Transmission line detection method, route strategy generation method and proxy server | |
| EP4331211A1 (en) | Consistent hashing for communication devices | |
| CN109600452B (en) | Server cluster, message pushing method and related server |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |