CN112822247B - System asynchronous communication method, device, electronic equipment and computer readable medium - Google Patents

System asynchronous communication method, device, electronic equipment and computer readable medium Download PDF

Info

Publication number
CN112822247B
CN112822247B CN202011629652.3A CN202011629652A CN112822247B CN 112822247 B CN112822247 B CN 112822247B CN 202011629652 A CN202011629652 A CN 202011629652A CN 112822247 B CN112822247 B CN 112822247B
Authority
CN
China
Prior art keywords
notification
service node
target
data
pool
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
Application number
CN202011629652.3A
Other languages
Chinese (zh)
Other versions
CN112822247A (en
Inventor
张鑫
崔金鹏
刘柳
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Xinao Shuneng Technology Co Ltd
Original Assignee
Xinao Shuneng Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Xinao Shuneng Technology Co Ltd filed Critical Xinao Shuneng Technology Co Ltd
Priority to CN202011629652.3A priority Critical patent/CN112822247B/en
Publication of CN112822247A publication Critical patent/CN112822247A/en
Application granted granted Critical
Publication of CN112822247B publication Critical patent/CN112822247B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

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/10—Protocols in which an application is distributed across nodes in the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
    • 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/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Abstract

The embodiment of the disclosure discloses a system asynchronous communication method, a device, electronic equipment and a computer readable medium. One embodiment of the method comprises: informing the service node set to a registration center; selecting at least one service node from the service node set as a target service node to obtain a target service node set; acquiring the number of data in a notification pool to be executed; based on the number, sending an execution notification to each target serving node in the set of target serving nodes. The implementation mode realizes asynchronous communication, and avoids the problem of data inconsistency between systems caused by simple asynchronous communication failure. By paying attention to the number of data in the notification pool to be executed, the system operation can be monitored under the condition of rapid increase of the traffic, and the system response is prevented from being slowed down. Therefore, the asynchronous communication has unified standard management, the management cost is reduced, and the user experience is indirectly improved.

Description

System asynchronous communication method, device, electronic equipment and computer readable medium
Technical Field
The embodiment of the disclosure relates to the technical field of computers, in particular to a system asynchronous communication method, a device, electronic equipment and a computer readable medium.
Background
With the increase of services and the increase of service complexity, the asynchronous communication scenes between systems are more and more, and the problem of a plurality of pain points cannot be solved. For example, simple asynchronous communication may fail, resulting in data inconsistency between systems. For another example, in the case of a rapid increase in traffic, a large burden is imposed on the system, resulting in a slow response of the system. Asynchronous communication is not unified in specification, so that management cost is high, execution progress cannot be captured, and manual intervention cost is high when problems occur.
Disclosure of Invention
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
Some embodiments of the present disclosure provide a system asynchronous communication method, apparatus, electronic device and computer readable medium to solve the technical problems mentioned in the background section above.
In a first aspect, some embodiments of the present disclosure provide a method for system asynchronous communication, the method including: informing the service node set to a registration center; selecting at least one service node from the service node set as a target service node to obtain a target service node set; acquiring the number of data in a notification pool to be executed; based on the number, sending an execution notification to each target serving node in the set of target serving nodes.
In a second aspect, some embodiments of the present disclosure provide a system asynchronous communication device, comprising: a notification unit configured to notify the service node set to the registry; the selecting unit is configured to select at least one service node from the service node set as a target service node to obtain a target service node set; an acquisition unit configured to acquire the number of data in a notification pool to be executed; a sending unit configured to send an execution notification to each target serving node in the set of target serving nodes based on the number.
In a third aspect, some embodiments of the present disclosure provide an electronic device, comprising: one or more processors; a storage device having one or more programs stored thereon which, when executed by one or more processors, cause the one or more processors to implement the method as described in the first aspect.
In a fourth aspect, some embodiments of the disclosure provide a computer readable medium having a computer program stored thereon, wherein the program, when executed by a processor, implements the method as described in the first aspect.
One of the above-described various embodiments of the present disclosure has the following advantageous effects: and selecting a target service node from the service node set by collecting the task notification service nodes to the registration center. And then, sending an execution notice to the target service node in the target service node set according to the number of the data in the notice pool to be executed. The method provided by the embodiment realizes asynchronous communication, and avoids the problem of data inconsistency between systems caused by simple asynchronous communication failure. By paying attention to the number of data in the notification pool to be executed, the system operation can be monitored under the condition of rapid increase of the traffic, and the system response is prevented from being slowed down. Therefore, the asynchronous communication has unified standard management, the management cost is reduced, and the user experience is indirectly improved.
Drawings
The above and other features, advantages and aspects of various embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and elements are not necessarily drawn to scale.
FIG. 1 is a schematic diagram of an application scenario of a system asynchronous communication method according to some embodiments of the present disclosure;
fig. 2 is a flow diagram of some embodiments of a system asynchronous communication method according to the present disclosure;
FIG. 3 is a schematic block diagram of some embodiments of a system asynchronous communication device according to the present disclosure;
FIG. 4 is a schematic block diagram of an electronic device suitable for use in implementing some embodiments of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it is to be understood that the disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided for a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and the embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be noted that, for convenience of description, only the portions related to the related invention are shown in the drawings. The embodiments and features of the embodiments in the present disclosure may be combined with each other without conflict.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence of the functions performed by the devices, modules or units.
It is noted that references to "a", "an", and "the" modifications in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will recognize that "one or more" may be used unless the context clearly dictates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
The present disclosure will be described in detail below with reference to the accompanying drawings in conjunction with embodiments.
Fig. 1 is a schematic diagram of an application scenario of a system asynchronous communication method according to some embodiments of the present disclosure.
In the application scenario of fig. 1, first, the computing device 101 may notify the service node collection 102 to the registry 103. Then, the computing device 101 may select at least one service node from the set of service nodes 102 as a target service node, resulting in a set of target service nodes 104. Thereafter, the computing device 101 can obtain the number 105 of data in the to-be-executed notification pool. Finally, based on the number 105, the computing device 101 may send an execution notification 106 to each target service node in the set of target service nodes.
The computing device 101 may be hardware or software. When the computing device is hardware, it may be implemented as a distributed cluster composed of multiple servers or terminal devices, or may be implemented as a single server or a single terminal device. When the computing device is embodied as software, it may be installed in the hardware devices enumerated above. It may be implemented, for example, as multiple software or software modules to provide distributed services, or as a single software or software module. And is not particularly limited herein.
It should be understood that the number of computing devices in FIG. 1 is merely illustrative. There may be any number of computing devices, as implementation needs dictate.
With continued reference to fig. 2, a flow 200 of some embodiments of a system asynchronous communication method according to the present disclosure is shown. The method may be performed by the computing device 101 of fig. 1. The asynchronous communication method of the system comprises the following steps:
step 201, notifying the service node to gather to the registry.
In some embodiments, the executing agent of the system asynchronous communication method (e.g., computing device 101 shown in FIG. 1) initiates the registry and aggregates the task notification service nodes to the registry.
Step 202, selecting at least one service node from the service node set as a target service node, and obtaining a target service node set.
In some embodiments, the executing entity may select at least one service node from the service node set as a target service node to obtain a target service node set by: in a first step, the execution agent may control the service nodes in the service node set to contend for execution opportunities at a timing (e.g., at a time interval of 5 minutes); secondly, in response to the fact that the competition is finished, the execution main body can control the service nodes which are not successfully contended to wait for the next competition; and thirdly, the execution body can determine the service node which is successfully contended as the target service center to obtain the target service node set.
Step 203, acquiring the number of data in the notification pool to be executed.
In some embodiments, the execution main body may obtain the number of data in the notification pool to be executed through a wired connection manner or a wireless connection manner.
It is noted that the wireless connection means may include, but is not limited to, a 3G/4G connection, a WiFi connection, a bluetooth connection, a WiMAX connection, a Zigbee connection, a UWB (ultra wideband) connection, and other wireless connection means now known or developed in the future.
Step 204, based on the number, sending an execution notification to each target service node in the set of target service nodes.
In some embodiments, the execution agent may send the execution notification to each target service node in the set of target service nodes by: in a first step, in response to determining that the number of data in the notification pool to be executed is smaller than a preset number (for example, 100 pieces), the execution main body may obtain the number of data in the notification pool; in response to determining that the data in the notification pool is smaller than the preset number, the execution main body may transfer the data in the notification pool to be executed; third, in response to determining that the number of data in the to-be-executed notification pool is greater than or equal to the preset number, the execution main body may send an execution notification to each target service node in the target service node set.
In some optional implementations of some embodiments, the method further comprises: determining a notification type of the execution notification in response to determining that the execution notification is sent; based on the notification type, the execution principal may control each target service node in the set of target service nodes to execute the execution notification.
In some optional implementations of some embodiments, the notification type includes, but is not limited to, one of the following types: periodic notification, timed notification, abnormal notification, custom notification, and continuous compensation notification.
The periodic class notification set forth above may be described as follows: the service node sends a data request to the third-party service at regular time when taking the periodic notification, if the request is successful, the success time and the sending times are recorded, if the request is failed, the execution times are judged, and if the request is greater than the preset times, the notification is finished according to the strategy (waiting for the next service node to rob the notification again to execute).
The timing notification set forth above may be described as follows: the service node receives the timing notice to judge whether the current time accords with the current execution time, if so, the service node initiates a request to a third party, and if not, the service node finishes the notice; and if the request of the third party is successfully sent, updating the notification time, and if the request fails, updating the notification state.
The exception class notification set forth above may be described as follows: the service node receives the abnormal notification and initiates a data request to the third-party service, if the data request is successful, the success time is recorded, if the data request is failed, the short message is pushed to a related responsible person, the state after the execution of the abnormal notification is updated, and the state is recorded in the notification pool.
The custom class notification set forth above may be described as follows: the service node receives the custom notification and initiates a data request to a third-party service, if the request is successful, the success time is recorded, if the request is failed, whether the custom notification needs to repeatedly send the request is judged, if the request is not needed, the notification is finished according to a finishing strategy, if the request needs to be repeatedly sent, whether the repeated times is larger than the preset times is judged, if the repeated times is larger than the preset times, the notification is finished according to the finishing strategy, and if the repeated times is smaller than the preset times, the data request is continuously initiated to the third-party service after waiting for the preset time.
The persistent compensation notification set forth above may be described as follows: the service node takes the compensation type notice to initiate a data request to the third-party service, if the data request is successful, the success time is recorded, and if the data request is not successful, the data request is according to 3 multiplied by 2 n-1 Calculating the next request time (minute), n represents the number of requests, 3 × 2 n-1 If the request succeeds next time, the success time (minute) is recorded, if the request fails, n +1 is calculated to be 3 × 2 n-1 At a later time (minute), the request continues to be sent, if n>And 4, if the request is not successful, stopping the request and waiting for the next service node to rob again to notify for execution.
One of the above-described various embodiments of the present disclosure has the following advantageous effects: and selecting a target service node from the service node set by collecting the task notification service nodes to the registration center. And then, sending an execution notice to the target service node in the target service node set according to the number of the data in the notice pool to be executed. The method provided by the embodiment realizes asynchronous communication, and avoids the problem of data inconsistency between systems caused by simple asynchronous communication failure. By paying attention to the number of data in the notification pool to be executed, the system operation can be monitored under the condition of the rapid increase of the traffic, and the system response is prevented from being slowed down. Therefore, the asynchronous communication has unified standard management, the management cost is reduced, and the user experience is indirectly improved.
With further reference to fig. 3, as an implementation of the above method for the above figures, the present disclosure provides some embodiments of a system asynchronous communication device, which correspond to the above method embodiments of fig. 2, and which can be applied in various electronic devices.
As shown in fig. 3, the system asynchronous communication device 300 of some embodiments includes: a notification unit 301, a selection unit 302, an acquisition unit 303, and a transmission unit 304. Wherein, the notification unit 301 is configured to notify the service node set to the registry; a selecting unit 302, configured to select at least one service node from the service node set as a target service node, resulting in a target service node set; an obtaining unit 303 configured to obtain the number of data in the notification pool to be executed; a sending unit 304 configured to send an execution notification to each target serving node in the set of target serving nodes based on the number.
In some alternative implementations of some embodiments, the selecting unit 302 of the system asynchronous communication device 300 includes: a first control subunit configured to control service nodes in the set of service nodes to periodically contend for execution opportunities; a second control subunit, configured to, in response to determining that the contention is over, control the service node that is not contended successfully to wait for the next contention; and the determining subunit is configured to determine the service node with successful contention as the target service node, so as to obtain the target service node set.
In some optional implementations of some embodiments, the sending unit 304 of the system asynchronous communication device 300 includes: an acquisition subunit configured to acquire, in response to the number being smaller than a preset number, a number of data in the notification pool; a transfer subunit configured to transfer the data in the notification pool to the to-be-executed notification pool in response to determining that the number of data in the notification pool is less than the preset number; a sending subunit configured to send an execution notification to each target service node in the set of target service nodes in response to determining that the number of data in the to-be-executed notification pool is greater than or equal to the preset number.
In some optional implementations of some embodiments, the system asynchronous communication device 300 is further configured to: in response to determining that the execution notification transmission is complete, determining a notification type of the execution notification; and controlling each target service node in the target service node set to execute the execution notification based on the notification type.
In some optional implementations of some embodiments, the notification type includes one of the following types: periodic notification, timed notification, abnormal notification, custom notification, and continuous compensation notification.
It will be appreciated that the above-described, the units described in the apparatus 300 correspond to the various steps in the method described with reference to fig. 2. Thus, the operations, features and advantages described above with respect to the method are also applicable to the apparatus 300 and the units included therein, and are not described herein again.
Referring now to FIG. 4, a block diagram of an electronic device (e.g., computing device 101 of FIG. 1) 400 suitable for use in implementing some embodiments of the present disclosure is shown. The server shown in fig. 4 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.
As shown in fig. 4, electronic device 400 may include a processing device (e.g., central processing unit, graphics processor, etc.) 401 that may perform various appropriate actions and processes in accordance with a program stored in a Read Only Memory (ROM) 402 or a program loaded from a storage device 408 into a Random Access Memory (RAM) 403. In the RAM403, various programs and data necessary for the operation of the electronic apparatus 400 are also stored. The processing device 401, the ROM 402, and the RAM403 are connected to each other via a bus 404. An input/output (I/O) interface 405 is also connected to bus 404.
Generally, the following devices may be connected to the I/O interface 405: input devices 406 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; an output device 407 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 408 including, for example, tape, hard disk, etc.; and a communication device 409. The communication means 409 may allow the electronic device 400 to communicate wirelessly or by wire with other devices to exchange data. While fig. 4 illustrates an electronic device 400 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided. Each block shown in fig. 4 may represent one device or may represent multiple devices as desired.
In particular, according to some embodiments of the present disclosure, the processes described above with reference to the flow diagrams may be implemented as computer software programs. For example, some embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer-readable medium, the computer program comprising program code for performing the method illustrated by the flow chart. In some such embodiments, the computer program may be downloaded and installed from a network through communications device 409, or installed from storage device 408, or installed from ROM 402. The computer program, when executed by the processing apparatus 401, performs the above-described functions defined in the methods of some embodiments of the present disclosure.
It should be noted that the computer readable medium described above in some embodiments of the present disclosure may be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, 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), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In some embodiments of the disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In some embodiments of the present disclosure, however, a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be embodied in the apparatus; or may exist separately without being assembled into the electronic device. The computer readable medium carries one or more programs which, when executed by the electronic device, cause the electronic device to: informing the service node set to a registration center; selecting at least one service node from the service node set as a target service node to obtain a target service node set; acquiring the number of data in a notification pool to be executed; based on the number, sending an execution notification to each target serving node in the set of target serving nodes.
Computer program code for carrying out operations for embodiments of the present disclosure may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C + +, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code 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).
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 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 described in some embodiments of the present disclosure may be implemented by software, and may also be implemented by hardware. The described units may also be provided in a processor, and may be described as: a processor includes a notification unit, a selection unit, an acquisition unit, and a transmission unit. Where the names of these elements do not in some cases constitute a limitation on the elements themselves, for example, a notification element may also be described as a "notification service node aggregated to a registry element".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems on a chip (SOCs), complex Programmable Logic Devices (CPLDs), and the like.
The foregoing description is only exemplary of the preferred embodiments of the disclosure 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 in the embodiments of the present disclosure is not limited to the specific combination of the above-mentioned features, but also encompasses other embodiments in which any combination of the above-mentioned features or their equivalents is made without departing from the inventive concept as defined above. For example, the above features and (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure are mutually replaced to form the technical solution.

Claims (6)

1. A system asynchronous communication method, comprising:
informing the service node set to a registration center;
selecting at least one service node from the service node set as a target service node to obtain a target service node set;
acquiring the number of data in a notification pool to be executed;
based on the number, sending an execution notification to each target serving node in the set of target serving nodes;
the selecting at least one service node from the service node set as a target service node to obtain a target service node set includes:
controlling service nodes in the service node set to contend for execution opportunities at regular time;
in response to the fact that the competition is over, controlling the service nodes which are not successfully contended to wait for the next competition;
determining the service node which is successfully contended as the target service node to obtain the target service node set;
the sending an execution notification to each target serving node in the set of target serving nodes based on the number comprises:
responding to the number smaller than the preset number, and acquiring the number of the data in the notification pool;
in response to determining that the number of data in the notification pool is less than the preset number, transferring the data in the notification pool to the to-be-executed notification pool;
and in response to determining that the number of data in the notification pool to be executed is greater than or equal to the preset number, sending an execution notification to each target service node in the target service node set.
2. The method of claim 1, further comprising:
in response to determining that the execution notification transmission is complete, determining a notification type of the execution notification;
and controlling each target service node in the target service node set to execute the execution notification based on the notification type.
3. The method of claim 2, wherein the notification type comprises one of: periodic notification, timed notification, abnormal notification, custom notification, and continuous compensation notification.
4. A system asynchronous communication device, comprising:
a notification unit configured to notify the service node set to the registry;
the selecting unit is configured to select at least one service node from the service node set as a target service node to obtain a target service node set;
an acquisition unit configured to acquire the number of data in a notification pool to be executed;
a sending unit configured to send an execution notification to each target serving node in the set of target serving nodes based on the number;
the selection unit includes:
a first control subunit configured to control service nodes in the set of service nodes to periodically contend for execution opportunities;
a second control subunit, configured to, in response to determining that the contention is over, control the service node that is not contended successfully to wait for the next contention;
a determining subunit configured to determine a service node with successful contention as the target service node, resulting in the target service node set;
the transmitting unit includes:
an acquisition subunit configured to acquire, in response to the number being smaller than a preset number, a number of data in the notification pool;
a transfer subunit configured to transfer the data in the notification pool to the to-be-executed notification pool in response to determining that the number of data in the notification pool is less than the preset number;
a sending subunit configured to send an execution notification to each target service node in the set of target service nodes in response to determining that the number of data in the to-be-executed notification pool is greater than or equal to the preset number.
5. An electronic device, comprising:
one or more processors;
a storage device having one or more programs stored thereon;
when executed by the one or more processors, cause the one or more processors to implement the method of any one of claims 1-3.
6. A computer-readable medium, on which a computer program is stored, wherein the program, when executed by a processor, implements the method of any one of claims 1-3.
CN202011629652.3A 2020-12-31 2020-12-31 System asynchronous communication method, device, electronic equipment and computer readable medium Active CN112822247B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011629652.3A CN112822247B (en) 2020-12-31 2020-12-31 System asynchronous communication method, device, electronic equipment and computer readable medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011629652.3A CN112822247B (en) 2020-12-31 2020-12-31 System asynchronous communication method, device, electronic equipment and computer readable medium

Publications (2)

Publication Number Publication Date
CN112822247A CN112822247A (en) 2021-05-18
CN112822247B true CN112822247B (en) 2023-04-07

Family

ID=75855063

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011629652.3A Active CN112822247B (en) 2020-12-31 2020-12-31 System asynchronous communication method, device, electronic equipment and computer readable medium

Country Status (1)

Country Link
CN (1) CN112822247B (en)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105101412A (en) * 2014-05-21 2015-11-25 中兴通讯股份有限公司 Notification message sending method and device
CN106330987A (en) * 2015-06-15 2017-01-11 交通银行股份有限公司 Dynamic load balancing method
CN107483470A (en) * 2017-09-04 2017-12-15 李黎明 Information on services shares Notification Method and device
CN107678622A (en) * 2017-09-27 2018-02-09 努比亚技术有限公司 A kind of display methods of application icon, terminal and storage medium
CN108121580A (en) * 2016-11-28 2018-06-05 腾讯科技（深圳）有限公司 The implementation method and device of application notification service
CN110601952A (en) * 2018-06-12 2019-12-20 北京京东尚科信息技术有限公司 Multi-channel message notification sending method and device
CN111400062A (en) * 2020-03-12 2020-07-10 苏州浪潮智能科技有限公司 Information notification method, device, system and computer readable storage medium
CN111737367A (en) * 2020-07-24 2020-10-02 国网区块链科技(北京)有限公司 Chain network fused distributed energy station information processing method and device
CN111767347A (en) * 2020-07-27 2020-10-13 腾讯科技（深圳）有限公司 Switching method and device of consensus algorithm, node equipment and storage medium
WO2020238190A1 (en) * 2019-05-30 2020-12-03 华为技术有限公司 Method for transmitting data, node, and storage medium

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105101412A (en) * 2014-05-21 2015-11-25 中兴通讯股份有限公司 Notification message sending method and device
CN106330987A (en) * 2015-06-15 2017-01-11 交通银行股份有限公司 Dynamic load balancing method
CN108121580A (en) * 2016-11-28 2018-06-05 腾讯科技（深圳）有限公司 The implementation method and device of application notification service
CN107483470A (en) * 2017-09-04 2017-12-15 李黎明 Information on services shares Notification Method and device
CN107678622A (en) * 2017-09-27 2018-02-09 努比亚技术有限公司 A kind of display methods of application icon, terminal and storage medium
CN110601952A (en) * 2018-06-12 2019-12-20 北京京东尚科信息技术有限公司 Multi-channel message notification sending method and device
WO2020238190A1 (en) * 2019-05-30 2020-12-03 华为技术有限公司 Method for transmitting data, node, and storage medium
CN111400062A (en) * 2020-03-12 2020-07-10 苏州浪潮智能科技有限公司 Information notification method, device, system and computer readable storage medium
CN111737367A (en) * 2020-07-24 2020-10-02 国网区块链科技(北京)有限公司 Chain network fused distributed energy station information processing method and device
CN111767347A (en) * 2020-07-27 2020-10-13 腾讯科技（深圳）有限公司 Switching method and device of consensus algorithm, node equipment and storage medium

Also Published As

Publication number Publication date
CN112822247A (en) 2021-05-18

Similar Documents

Publication Publication Date Title
CN111246228B (en) Method, device, medium and electronic equipment for updating gift resources of live broadcast room
CN112416632B (en) Event communication method and device, electronic equipment and computer readable medium
CN112256733A (en) Data caching method and device, electronic equipment and computer readable storage medium
CN111294385A (en) Data transmission method and device, readable medium and electronic equipment
CN114090316A (en) Memory fault processing method and device, storage medium and electronic equipment
CN110795446A (en) List updating method and device, readable medium and electronic equipment
CN113760536A (en) Data caching method and device, electronic equipment and computer readable medium
CN112907942A (en) Vehicle scheduling method, device, equipment and medium based on edge calculation
CN109428926B (en) Method and device for scheduling task nodes
CN113110152A (en) Unmanned vehicle driving state switching method and device, electronic equipment and medium
WO2024066374A1 (en) Service degradation method and apparatus, device, computer-readable medium and program product
CN112822247B (en) System asynchronous communication method, device, electronic equipment and computer readable medium
CN113553206B (en) Data event execution method and device, electronic equipment and computer readable medium
CN114785770A (en) Mirror layer file sending method and device, electronic equipment and computer readable medium
CN112543228A (en) Data transmission method and device, electronic equipment and computer readable medium
CN112307071A (en) Monitoring data acquisition method and device, electronic equipment and computer readable medium
CN114745276B (en) Switch bandwidth adjusting method and device, electronic equipment and computer readable medium
CN113535428B (en) Method, device, equipment and medium for processing request message and response message
CN113784097B (en) Key generation and distribution method, device, electronic equipment and computer readable medium
CN113378041B (en) Prompt message pushing method, device, electronic equipment and computer readable medium
CN113438284B (en) Request processing method and device, electronic equipment and computer readable medium
CN114637524A (en) Host monitoring data acquisition method, device, equipment and computer readable medium
CN115914399A (en) Request data transmission method, device, equipment, medium and program product
CN114172946A (en) Request result sending method and device, electronic equipment and computer readable medium
CN113934599A (en) Information processing method, device, electronic equipment and computer readable medium

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