CN111343272B

CN111343272B - Cross-node request retry method of star network architecture and electronic equipment

Info

Publication number: CN111343272B
Application number: CN202010121670.4A
Authority: CN
Inventors: 何保良
Original assignee: Hangzhou Tuya Information Technology Co Ltd
Current assignee: Hangzhou Tuya Information Technology Co Ltd
Priority date: 2020-02-26
Filing date: 2020-02-26
Publication date: 2023-02-07
Anticipated expiration: 2040-02-26
Also published as: CN111343272A

Abstract

The disclosure relates to a cross-node request retry method and an electronic device of a star network architecture, wherein the method comprises the following steps: sending a remote procedure call request to a target node; determining a proxy node from a star network architecture in response to the remote procedure call request failing; forwarding, by the proxy node, the remote procedure call request to the target node. The embodiment of the disclosure can improve the success rate of RPC requests.

Description

Cross-node request retry method of star network architecture and electronic equipment

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a cross-node request retry method and an electronic device for a star network architecture.

Background

Currently, cross-node Remote Procedure Call (RPC) is a very common phenomenon, and in a star network architecture, when a node needs to perform processing through other nodes, an RPC request can be sent to the node, and if no response is obtained, the request can be sent continuously. If the node equipment has a fault or network fault, network paralysis can be caused by repeatedly sending the RPC request, and the success rate of the RPC request is low.

Disclosure of Invention

The disclosure provides a cross-node request retry method of a star network architecture and an electronic device, which can improve the success rate of node communication and reduce the occupation of network resources.

According to an aspect of the present disclosure, there is provided a cross-node request retry method of a star network architecture, including:

sending a remote procedure call request to a target node;

responding to the remote procedure call request failure, and determining a proxy node from a star network architecture;

forwarding, by the proxy node, the remote procedure call request to the target node.

In some possible embodiments, the method further comprises the step of determining that the remote procedure call request failed, including at least one of:

determining that the remote procedure call request fails when no response information corresponding to the procedure call request is received within a preset time after the procedure call request is sent to the target node;

and determining that the remote procedure call request fails when a network fault with the target node is detected.

In some possible embodiments, the determining a proxy node from a star network architecture in response to the remote procedure call request failure comprises:

acquiring response time of each node in a star network architecture aiming at a source node, wherein the source node is a node which needs to send a process calling request to a target node;

and determining the node with the shortest response time as the proxy node.

In some possible embodiments, the obtaining the response time of each node in the star network architecture for the source node includes:

and determining the response time of each node aiming at the source node according to the stored average response time of each node aiming at the source node to send the request information in the star network architecture.

In some possible embodiments, the method further comprises: and determining the next proxy node according to the response time of each node under the condition that the remote procedure call request is unsuccessfully forwarded to the target node through the proxy node with the shortest response time.

According to a second aspect of the present disclosure, there is provided an electronic device, a node within a star network architecture, comprising:

the request module is used for sending a remote procedure call request to the target node;

the determining module is used for determining a proxy node from a star network architecture in response to the remote procedure call request failure;

a forwarding module, configured to forward the remote procedure call request to the target node through the proxy node.

In some possible embodiments, the step of determining, by the determination module, that the remote procedure call request failed comprises at least one of:

determining that the remote procedure call request fails when response information corresponding to the procedure call request is not received within a preset time after the procedure call request is sent to the target node;

and determining that the remote procedure call request fails under the condition that a network fault between the remote procedure call request and the target node is detected.

In some possible embodiments, the determining module is further configured to acquire response time of each node in the star network architecture for a source node, where the source node is a node that needs to send a procedure call request to the target node;

and determining the node with the shortest response time as the proxy node.

In some possible embodiments, the determining module is further configured to determine the response time of each node for the source node according to an average response time of each node in the star network architecture for the source node to send information within a stored preset time.

In some possible embodiments, the determining module is further configured to determine, when the proxy node with the shortest response time fails to forward the remote procedure call request to the target node, a next proxy node according to the response time of each node.

In the embodiment of the disclosure, when each node of the star network architecture executes Remote Procedure Call (RPC) of a target node, the Remote Procedure Call (RPC) can be forwarded by using other nodes in the star network architecture as proxy nodes under the condition that the request fails, so that the success rate of RPC in the star network can be improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.

Other features and aspects of the present disclosure will become apparent from the following detailed description of exemplary embodiments, which proceeds with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the disclosure.

FIG. 1 shows a flow diagram of a cross-node request retry method of a star network architecture according to an embodiment of the present disclosure;

FIG. 2 shows a schematic structural diagram of a star network architecture according to an embodiment of the present disclosure;

fig. 3 shows a flow chart of step S20 in a cross-node request retry method in a star network architecture according to an embodiment of the present disclosure;

FIG. 4 shows a block diagram of an electronic device according to an embodiment of the disclosure;

FIG. 5 shows a block diagram of an electronic device 800 in accordance with an embodiment of the disclosure;

fig. 6 illustrates a block diagram of another electronic device 1900 in accordance with an embodiment of the disclosure.

Detailed Description

Various exemplary embodiments, features and aspects of the present disclosure will be described in detail below with reference to the accompanying drawings. In the drawings, like reference numbers indicate functionally identical or similar elements. While the various aspects of the embodiments are presented in drawings, the drawings are not necessarily drawn to scale unless specifically indicated.

The word "exemplary" is used exclusively herein to mean "serving as an example, embodiment, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.

The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the term "at least one" herein means any one of a plurality or any combination of at least two of a plurality, for example, including at least one of a, B, and C, and may mean including any one or more elements selected from the group consisting of a, B, and C.

Furthermore, in the following detailed description, numerous specific details are set forth in order to provide a better understanding of the present disclosure. It will be understood by those skilled in the art that the present disclosure may be practiced without some of these specific details. In some instances, methods, means, elements and circuits that are well known to those skilled in the art have not been described in detail so as not to obscure the present disclosure.

An execution main body of the cross-node request retry method of the star network architecture provided by the embodiment of the present disclosure may be an electronic device under any star network architecture, for example, the execution main body may be a terminal device or a server, where the terminal device may be a User Equipment (UE), a mobile device, a User terminal, a cellular phone, a cordless phone, a Personal Digital Assistant (PDA), a handheld device, a computing device, an in-vehicle device, a wearable device, and the like. In some possible implementations, the cross-node request retry method of the star network architecture may be implemented by a processor invoking computer-readable instructions stored in a memory.

Fig. 1 shows a flowchart of a cross-node request retry method of a star network architecture according to an embodiment of the present disclosure, and as shown in fig. 1, the cross-node request retry method of the star network architecture includes:

s10: sending a remote procedure call request to a target node;

s20: determining a proxy node from a star network architecture in response to the remote procedure call request failing;

s30: forwarding, by the proxy node, the remote procedure call request to the target node.

As described in the foregoing embodiment, the cross-node request retry method according to the embodiment of the present disclosure may be applied to a star network structure, and fig. 2 illustrates a schematic structural diagram of a star network architecture according to the embodiment of the present disclosure, where the star network architecture may include five node devices a, B, C, D, and E, where the nodes may communicate with each other, and each node may be a server or may also be an electronic device of another type.

As shown in FIG. 2, node A may be acting as a source node for performing remote procedure calls to target node C, i.e., a remote procedure call request (RPC request) may be sent to target node C. In some possible embodiments, the source node a may request the node C to perform an operation or other processing operation according to a request of a client connected thereto or according to a data processing procedure to be performed by the source node a, at which point an RPC request may be sent to the target node C, where the RPC request may include an address of the source node a, an address of the target node C, and may further include information such as an identification of an operation (e.g., a name of a function, a name of an operation, etc.) performed by the called target node C, and a relevant numerical parameter.

In some possible embodiments, if the target node C can receive the RPC request sent by the source node a, the corresponding processing operation may be correspondingly performed, and the returned response information is sent to the source node a. The response information may include a processing result of the RPC request, or may also include information of successful execution, which may be determined according to different processing operations, and this disclosure does not specifically limit this.

In other embodiments, there may be a case of device failure or network failure, which results in that the RPC request of the source node cannot be successfully sent to the target node, or the target node cannot successfully execute corresponding processing to return response information to the source node, which results in a case of request failure. At the moment, the agent node can be selected from the star network architecture, the RPC request is forwarded, and the success rate of the RPC is improved.

The mode for determining the RPC request failure may include at least one of the following modes:

a) Determining that the remote procedure call request fails when response information corresponding to the procedure call request is not received within a preset time after the procedure call request is sent to the target node;

in some possible embodiments, the timing may be started after the RPC request is sent, and if the response information for the RPC request returned from the target node is not received within a preset time, it may be determined that the RPC request fails. The preset time may be a preset value, for example, 5 seconds, or may also be another time threshold, which is not specifically limited in this disclosure.

B) Determining that the remote procedure call request fails when a network fault with the target node is detected;

in some possible embodiments, the current network status may be detected, and if a network status failure is detected, such as a failure to access the DNS server, or a power failure of the network interface of the source node device is detected, the network failure may be determined, and the RPC request may be determined to have failed.

Based on the above configuration, it can be determined that the RPC request fails, and at this time, the RPC request can be forwarded through the proxy node.

Fig. 3 shows a flowchart of step S20 in a cross-node request retry method in a star network architecture according to an embodiment of the present disclosure, wherein the determining a proxy node from the star network architecture in response to the remote procedure call request failure includes:

s21: acquiring response time of each node in a star network architecture aiming at a source node, wherein the source node is a node which needs to send a process calling request to a target node;

s22: and determining the node with the shortest response time as the proxy node.

In some possible embodiments, the proxy node may be determined according to a response time of each node in the star network architecture to the source node. In the history process of the operation of the star network architecture, historical data of response time among nodes can be stored. For example, for the source node a, it may start timing when the source node a sends the first request to other nodes, and determine the time when the response information of the first request is received, and use the time as the history data of the response time. The above history data is stored in the node device to be read and recalled. In addition, the first request may be a request for performing an arbitrary operation. By the method, the historical data of the response time between any two nodes can be obtained.

The disclosed embodiments may determine the proxy node using an average of historical data of response times between the source node and other nodes. The average value of the response time of each node and the source node may be determined as the response time of each node for the source node, for example, the average value of the historical data of the response time of the node B for the source node a may be used as the response time of the node B for the node a, so that the response time between each node and the source node may be determined. The node having the smallest average value of the historical data of the response time with the source node can be determined as the proxy node. With this configuration, it is also possible to reduce the request time in the case of providing a success rate of RPC requests.

Further, in the case of the determined proxy node, the RPC request may be forwarded through the proxy node, and the source node may send forwarding information to the proxy node, where the forwarding information includes the RPC request to be transmitted, and an address of the source node and an address of the proxy node, so that the proxy node may be used to complete the forwarding of the RPC request. In the process of forwarding the RPC request, if the forwarding fails, the proxy node of the embodiment of the present disclosure may feed back the failure result to the source node. The manner of determining the forwarding failure is the same as the manner of determining the RPC request failure, and is not described herein again.

In the event that the source node determines that proxy node forwarding fails, a new proxy node may be reselected. The new proxy nodes may be determined according to the order of the average of the obtained historical data of the response time from small to large, and the node with the smallest response time except the failed proxy node is selected as the new proxy node. According to the method, the success rate of the RPC request can be further improved.

In addition, in the embodiment of the present disclosure, when the proxy node fails to forward the RPC request, the proxy node of the proxy node may also be selected according to the embodiment of the present disclosure, that is, the proxy node may be used as a source node, the proxy node of the source node is selected, and the RPC request is forwarded.

The retry procedure of the disclosed embodiment is illustrated below with reference to fig. 2 as an example. The source node A is used for sending an RPC request to the target node C, and under the condition that the RPC request is judged to fail, the proxy node B is selected from the star network architecture to forward the RPC request, wherein the adjacent node of the source node can be determined to be the proxy node through response time, and the proxy node B is selected to forward the RPC request. The source node A sends a forwarding request to the node B, and the proxy node B forwards the RPC request to the target node C according to the request to complete the forwarding of the RPC request.

In addition, each electronic device in the star network architecture of the embodiment of the present disclosure may be configured to execute the method, and the electronic device may determine whether to start the proxy forwarding function according to the received configuration selection information, and may receive and send an RPC request when the proxy forwarding function is started. The embodiment of the present disclosure may automatically start the proxy forwarding function when the electronic device is started, or may also receive configuration information transmitted from other devices (e.g., a control device) to perform switching between starting and stopping of the proxy forwarding function. In addition, in the embodiment of the present disclosure, each electronic device in the star network architecture may share the current state of the proxy forwarding function with each electronic device in the network when the proxy forwarding function changes, so that the electronic device in the network may obtain and store the turn-tables of the proxy forwarding functions of other electronic devices in real time, and when selecting a proxy node, may select a proxy node from the nodes that start the proxy forwarding function.

In summary, in the embodiment of the present disclosure, when each node of the star network architecture executes Remote Procedure Call (RPC) of a target node, when a request fails, other nodes in the star network architecture may serve as proxy nodes to help forward a remote call request, so that a success rate of RPC in the star network may be improved.

It will be understood by those skilled in the art that in the method of the present invention, the order of writing the steps does not imply a strict order of execution and any limitations on the implementation, and the specific order of execution of the steps should be determined by their function and possible inherent logic.

It is understood that the above-mentioned embodiments of the method of the present disclosure can be combined with each other to form a combined embodiment without departing from the principle logic, which is limited by the space, and the detailed description of the present disclosure is omitted.

In addition, the present disclosure also provides a cross-node request retry apparatus of a star network architecture, a star network architecture system, an electronic device, a computer readable storage medium, and a program, which can all be used to implement any one of the cross-node request retry methods of the star network architecture provided by the present disclosure, and the corresponding technical solutions and descriptions and corresponding descriptions in the method sections are not described again.

Fig. 4 shows a block diagram of an electronic device according to an embodiment of the present disclosure, which, as shown in fig. 4, may be an electronic device in a star network architecture, comprising:

a request module 10, configured to send a remote procedure call request to a target node;

a determining module 20, configured to determine a proxy node from a star network architecture in response to a failure of the remote procedure call request;

a forwarding module 30, configured to forward the remote procedure call request to the target node through the proxy node.

and determining the node with the shortest response time as the proxy node.

In some possible embodiments, the determining module is further configured to determine the response time of each node with respect to the source node according to an average response time of each node in the star network architecture for the source node to send information within the stored preset time.

In some embodiments, functions of or modules included in the apparatus provided in the embodiments of the present disclosure may be used to execute the method described in the above method embodiments, and specific implementation thereof may refer to the description of the above method embodiments, and for brevity, will not be described again here.

Embodiments of the present disclosure also provide a computer-readable storage medium, on which computer program instructions are stored, and when executed by a processor, the computer program instructions implement the above method. The computer readable storage medium may be a non-volatile computer readable storage medium.

An embodiment of the present disclosure further provides an electronic device, including: a processor; a memory for storing processor-executable instructions; wherein the processor is configured as the above method.

In addition, the embodiment of the present disclosure further provides a star network architecture system, where the system includes a plurality of electronic devices, each electronic device forms a star network architecture, and the electronic devices execute the method of the embodiment of the present disclosure.

The electronic device may be provided as a terminal, server, or other form of device.

Fig. 5 illustrates a block diagram of an electronic device 800 in accordance with an embodiment of the disclosure. For example, the electronic device 800 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, or the like terminal.

Referring to fig. 5, electronic device 800 may include one or more of the following components: processing component 802, memory 804, power component 806, multimedia component 808, audio component 810, input/output (I/O) interface 812, sensor component 814, and communications component 816.

The processing component 802 generally controls overall operation of the electronic device 800, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing components 802 may include one or more processors 820 to execute instructions to perform all or a portion of the steps of the methods described above. Further, the processing component 802 can include one or more modules that facilitate interaction between the processing component 802 and other components. For example, the processing component 802 can include a multimedia module to facilitate interaction between the multimedia component 808 and the processing component 802.

The memory 804 is configured to store various types of data to support operations at the electronic device 800. Examples of such data include instructions for any application or method operating on the electronic device 800, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 804 may be implemented by any type or combination of volatile or non-volatile memory devices, such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.

The power supply component 806 provides power to the various components of the electronic device 800. The power components 806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the electronic device 800.

The multimedia component 808 includes a screen that provides an output interface between the electronic device 800 and a user. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front facing camera and/or a rear facing camera. The front camera and/or the rear camera may receive external multimedia data when the electronic device 800 is in an operation mode, such as a shooting mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a Microphone (MIC) configured to receive external audio signals when the electronic device 800 is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signal may further be stored in the memory 804 or transmitted via the communication component 816. In some embodiments, audio component 810 also includes a speaker for outputting audio signals.

The I/O interface 812 provides an interface between the processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.

The sensor assembly 814 includes one or more sensors for providing various aspects of state assessment for the electronic device 800. For example, the sensor assembly 814 may detect an open/closed state of the electronic device 800, the relative positioning of components, such as a display and keypad of the electronic device 800, the sensor assembly 814 may also detect a change in the position of the electronic device 800 or a component of the electronic device 800, the presence or absence of user contact with the electronic device 800, orientation or acceleration/deceleration of the electronic device 800, and a change in the temperature of the electronic device 800. Sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 814 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

The communication component 816 is configured to facilitate wired or wireless communication between the electronic device 800 and other devices. The electronic device 800 may access a wireless network based on a communication standard, such as WiFi,2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 further includes a Near Field Communication (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, ultra Wideband (UWB) technology, bluetooth (BT) technology, and other technologies.

In an exemplary embodiment, the electronic device 800 may be implemented by one or more Application Specific Integrated Circuits (ASICs), digital Signal Processors (DSPs), digital Signal Processing Devices (DSPDs), programmable Logic Devices (PLDs), field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.

In an exemplary embodiment, a non-transitory computer-readable storage medium, such as the memory 804, is also provided that includes computer program instructions executable by the processor 820 of the electronic device 800 to perform the above-described methods.

Fig. 6 illustrates a block diagram of another electronic device 1900 in accordance with an embodiment of the disclosure. For example, electronic device 1900 may be provided as a server. Referring to fig. 6, electronic device 1900 includes a processing component 1922 further including one or more processors and memory resources, represented by memory 1932, for storing instructions, e.g., applications, that are executable by processing component 1922. The application programs stored in memory 1932 may include one or more modules that each correspond to a set of instructions. Further, the processing component 1922 is configured to execute instructions to perform the methods described above.

The electronic device 1900 may also include a power component 1926 configured to perform power management of the electronic device 1900, a wired or wireless network interface 1950 configured to connect the electronic device 1900 to a network, and an input/output (I/O) interface 1958. The electronic device 1900 may operate based on an operating system stored in memory 1932, such as Windows Server, mac OS XTM, unixTM, linuxTM, freeBSDTM, or the like.

In an exemplary embodiment, a non-transitory computer readable storage medium, such as the memory 1932, is also provided that includes computer program instructions executable by the processing component 1922 of the electronic device 1900 to perform the above-described methods.

The present disclosure may be systems, methods, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for causing a processor to implement various aspects of the present disclosure.

The computer-readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as a punch card or an in-groove protruding structure with instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or electrical signals transmitted through electrical wires.

The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device via a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.

The computer program instructions for carrying out operations of the present disclosure may be assembler instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, the electronic circuitry that can execute the computer-readable program instructions implements aspects of the present disclosure by utilizing the state information of the computer-readable program instructions to personalize the electronic circuitry, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA).

Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

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 disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). 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.

Having described embodiments of the present disclosure, the foregoing description is intended to be exemplary, not exhaustive, and not limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein were chosen in order to best explain the principles of the embodiments, the practical application, or technical improvements to the techniques in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.

Claims

1. A cross-node request retry method of a star network architecture is characterized by comprising the following steps:

sending a remote procedure call request to a target node;

in response to the remote procedure call request failing, determining a proxy node from a star network architecture, comprising:

acquiring response time of each node in a star network architecture to a source node, wherein the source node is a node which needs to send a process call request to a target node, and the method comprises the following steps:

determining the response time of each node aiming at the source node according to the stored average response time of each node aiming at the source node to send the request information in the star network architecture;

determining the node with the shortest response time as a proxy node;

2. The method of claim 1, further comprising the step of determining that the remote procedure call request failed, including at least one of:

3. The method according to claim 1 or 2, characterized in that the method further comprises: and determining the next proxy node according to the response time of each node under the condition that the remote procedure call request is unsuccessfully forwarded to the target node through the proxy node with the shortest response time.

4. An electronic device, a node within an electronic device star network architecture, comprising:

a determining module, configured to determine a proxy node from a star network architecture in response to a failure of the remote procedure call request, including:

determining the node with the shortest response time as a proxy node;

5. The electronic device of claim 4, wherein the determining module determines that the remote procedure call request failed comprises at least one of:

6. The electronic device according to claim 4 or 5, wherein the determining module is further configured to determine a next proxy node according to the response time of each node when the proxy node with the shortest response time fails to forward the remote procedure call request to the target node.