CN112272241B - Cloud computing message sending method and related device - Google Patents

Cloud computing message sending method and related device Download PDF

Info

Publication number
CN112272241B
CN112272241B CN202011305674.4A CN202011305674A CN112272241B CN 112272241 B CN112272241 B CN 112272241B CN 202011305674 A CN202011305674 A CN 202011305674A CN 112272241 B CN112272241 B CN 112272241B
Authority
CN
China
Prior art keywords
message
target node
cloud
cloud service
service client
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
CN202011305674.4A
Other languages
Chinese (zh)
Other versions
CN112272241A (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.)
Jindiyun Technology Co ltd
Original Assignee
Jindiyun 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 Jindiyun Technology Co ltd filed Critical Jindiyun Technology Co ltd
Priority to CN202011305674.4A priority Critical patent/CN112272241B/en
Publication of CN112272241A publication Critical patent/CN112272241A/en
Application granted granted Critical
Publication of CN112272241B publication Critical patent/CN112272241B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1008—Server selection for load balancing based on parameters of servers, e.g. available memory or workload
    • 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
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H04L67/1012—Server selection for load balancing based on compliance of requirements or conditions with available server resources
    • 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/14—Session management
    • H04L67/141—Setup of application sessions
    • 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/14—Session management
    • H04L67/143—Termination or inactivation of sessions, e.g. event-controlled end of session
    • H04L67/145—Termination or inactivation of sessions, e.g. event-controlled end of session avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H04L69/162—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields involving adaptations of sockets based mechanisms

Abstract

The application discloses a cloud computing message sending method, which comprises the following steps: the public cloud server is connected with a cloud service client of the target node; the target node is a node determined from a plurality of nodes according to node state information and client state information; and sending the message to be sent to the cloud service client of the target node, so that the cloud service client of the target node sends the message to be sent to a private cloud server. The cloud service client sends the message of the public cloud server to the private cloud server instead of directly exposing the interface of the private cloud server, so that the safety of message sending is improved, and the safety of the private cloud server is also maintained. The application also discloses a cloud computing message sending device, a server and a computer readable storage medium, which have the beneficial effects.

Description

Cloud computing message sending method and related device
Technical Field
The present application relates to the field of cloud computing technologies, and in particular, to a cloud computing message sending method, a cloud computing message sending device, a server, and a computer readable storage medium.
Background
With the continuous development of cloud computing technology, public and private clouds are emerging. Wherein the public cloud is a cloud computing environment provided by a cloud service vendor. Private clouds are the only channels that an enterprise has in possession of infrastructure resources. Hybrid cloud technology has emerged on the basis of public and private clouds, meaning that data and applications can be deployed or stored between private and public clouds, respectively, in a mobile manner. For example, a customer may choose to store data in a private cloud while running an application in a public cloud. The public cloud resources are fully utilized, the maintenance cost is reduced, and the security of sensitive confidential data is ensured. Further, there is a need to consider the process of message transmission between public and private clouds in a hybrid cloud.
In the related art, in order to realize that a message of a public cloud is sent to a private cloud. The proxy server comprises an http service interface, the public cloud sends the message to the proxy server, and the proxy server pushes the message to the private cloud server. The private cloud server can be directly mapped to the external network, the corresponding http service interface is exposed, and the public cloud server directly pushes the corresponding message to the private cloud server through the service interface. However, no way is provided for the proxy server exposure interface or the private cloud exposure interface to solve the data security problem in the private cloud, so that sensitive data in the private cloud is likely to be accessed, and the security is greatly reduced.
Therefore, how to improve the security of sending messages from public clouds to private clouds is a major concern for those skilled in the art.
Disclosure of Invention
The application aims to provide a cloud computing message sending method, a cloud computing message sending device, a server and a computer readable storage medium, wherein a cloud service client sends a message of a public cloud server to a private cloud server instead of directly exposing an interface of the private cloud server, so that the safety of message sending is improved, and the safety of the private cloud server is also maintained.
In order to solve the technical problems, the application provides a cloud computing message sending method, which comprises the following steps:
the public cloud server is connected with a cloud service client of the target node; the target node is a node determined from a plurality of nodes according to node state information and client state information;
and sending the message to be sent to the cloud service client of the target node, so that the cloud service client of the target node sends the message to be sent to a private cloud server.
Optionally, the method further comprises:
selecting a plurality of candidate nodes of the activated clients from the plurality of nodes;
and determining the target node from the candidate nodes of the plurality of activated clients according to the access frequency and the access time.
Optionally, the method further comprises:
and when the cloud service client of the target node is disconnected with the public cloud server, determining a new node from the plurality of nodes as a new target node so that the public cloud server is connected with the cloud service client of the new target node.
Optionally, the step of sending the message to be sent to the private cloud server by the cloud service client of the target node includes:
the cloud service client of the target node sends the message to be sent to cloud service clients of other nodes;
and the cloud service clients of the other nodes send the received message to be sent to the private cloud server.
Optionally, the method further comprises:
and when the message sending to the cloud service client of the other node fails, the cloud service client of the target node sends the message to be sent to the cloud service client of the next other node.
Optionally, the public cloud server is connected with a cloud service client of the target node, including:
and the public cloud server is connected with the cloud service client of the target node through websocket long connection.
Optionally, the cloud service client of the target node sends the message to be sent to cloud service clients of other nodes, including:
and the cloud service client of the target node sends the message to be sent to cloud service clients of other nodes through a TCP protocol.
The application also provides a cloud computing message sending device, which comprises:
the client connection module is used for connecting with a cloud service client of the target node; the target node is a node determined from a plurality of nodes according to node state information and client state information;
and the message sending module is used for sending the message to be sent to the cloud service client of the target node so that the cloud service client of the target node sends the message to be sent to the private cloud server.
The application also provides a server, comprising:
a memory for storing a computer program;
and a processor for implementing the steps of the cloud computing message sending method as described above when executing the computer program.
The present application also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the cloud computing message sending method as described above.
The cloud computing message sending method provided by the application comprises the following steps: the public cloud server is connected with a cloud service client of the target node; the target node is a node determined from a plurality of nodes according to node state information and client state information; and sending the message to be sent to the cloud service client of the target node, so that the cloud service client of the target node sends the message to be sent to a private cloud server.
The public cloud server is connected with the cloud service client of the target node, then the message to be sent is sent to the cloud service client of the target node, instead of the public cloud server directly sending the message to the private cloud server, and then the cloud service client of the target node sends the message to be sent to the private cloud server, so that the private cloud server receives the message sent by the public cloud server, instead of exposing the private cloud server interface and then sending the message, the reliability of access to the private cloud server is maintained, and the security of the private cloud server is improved.
The application also provides a cloud computing message sending device, a server and a computer readable storage medium, which have the advantages and are not described in detail herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only embodiments of the present application, and that other drawings may be obtained according to the provided drawings without inventive effort for a person skilled in the art.
Fig. 1 is a flowchart of a cloud computing message sending method according to an embodiment of the present application;
fig. 2 is a flowchart of another method for sending cloud computing messages according to an embodiment of the present application;
fig. 3 is a schematic structural diagram of a cloud computing message sending device according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of another cloud computing message sending device according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of a server according to an embodiment of the present application.
Detailed Description
The core of the application is to provide a cloud computing message sending method, a cloud computing message sending device, a server and a computer readable storage medium, wherein a cloud service client sends a message of a public cloud server to a private cloud server instead of directly exposing an interface of the private cloud server, so that the safety of message sending is improved, and the safety of the private cloud server is also maintained.
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more apparent, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it is apparent that the described embodiments are some embodiments of the present application, but not all embodiments of the present application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
In the related art, in order to realize that a message of a public cloud is sent to a private cloud. The proxy server comprises an http service interface, the public cloud sends the message to the proxy server, and the proxy server pushes the message to the private cloud server. The private cloud server can be directly mapped to the external network, the corresponding http service interface is exposed, and the public cloud server directly pushes the corresponding message to the private cloud server through the service interface. However, no way is provided for the proxy server exposure interface or the private cloud exposure interface to solve the data security problem in the private cloud, so that sensitive data in the private cloud is likely to be accessed, and the security is greatly reduced.
Therefore, the cloud computing message sending method provided by the application includes the steps that the public cloud server is connected with the cloud service client of the target node, then the message to be sent is sent to the cloud service client of the target node instead of the public cloud server directly sending the message to the private cloud server, then the cloud service client of the target node sends the message to be sent to the private cloud server, the private cloud server receives the message sent by the public cloud server instead of the message sent after exposing the private cloud server interface, the reliability of access to the private cloud server is maintained, and the security of the private cloud server is improved.
The following describes a cloud computing message sending method provided by the application through an embodiment.
Referring to fig. 1, fig. 1 is a flowchart of a cloud computing message sending method according to an embodiment of the present application.
In this embodiment, the method may include:
s101, a public cloud server is connected with a cloud service client of a target node; the target node is a node determined from a plurality of nodes according to the node state information and the client state information;
it can be seen that this step is mainly that the public cloud server is connected with the cloud service client of the target node, so that the public cloud server can send a message to the cloud service client of the target node.
In this embodiment, the method is mainly applied to a hybrid cloud, where the hybrid cloud is mainly formed by mixing a private cloud and a public cloud. The public cloud mainly comprises public cloud servers.
The cloud service client of the target node refers to a client program of a cloud service manufacturer for providing services for users. For example, saaS vendors offer clients to download installed desktop client programs. Generally, saaS manufacturers provide software service sites, so that users can access the software service sites through thin clients (browsers), and desktop client programs are provided to realize some enhanced functions (functions which cannot be realized by the browsers, such as document uploading and downloading, document conversion processing, message end transmission and the like). In the prior art, generally, a cloud service client can be directly connected with a public cloud server and a private cloud server. Therefore, the cloud service client of the target node in this embodiment may directly connect with the public cloud server and the private cloud server.
The target node may be a node determined from a plurality of nodes according to node state information and client state information, and is mainly used for selecting a node suitable as a target node from the plurality of nodes so as to improve the speed and performance of sending a message to the target node and keep the message of the public cloud server to be sent to the target node stably and reliably. The node state information refers to hardware state information of the node, and includes, but is not limited to, processor utilization, memory utilization, hardware temperature, and the like, so as to determine a node with a good node hardware state. The client state information refers to state information of client software installed in a node, and includes, but is not limited to, whether to activate, log in, and be in a connectable state, so as to determine a node with good client state. It can be seen that, by determining the node by the node state information and the client state information, a node having good hardware state and good software state can be selected as the node in this step.
In this step, the public cloud server and the client of the target node may be connected through tcp protocol, or may be connected through websocket long connection, or may be connected through http. It can be seen that the connection manner between the public cloud server and the client of the target node in this embodiment is not unique, and is not specifically limited herein.
In order to further improve the timeliness of the message sent after connection, the steps may include:
the public cloud server is connected with a cloud service client of the target node through websocket long connection.
Therefore, in the alternative scheme, the connection mode between the public cloud server and the target node is mainly described. Further, the target node is linked through a websocket long connection. websocket is a protocol that performs full duplex communications over a single TCP connection. The websocket enables data exchange between the client and the server to be simpler, and allows the server to actively push data to the client. In the websocket API, the browser and the server only need to complete one handshake, and can directly establish persistent connection between the two and perform bidirectional data transmission. Therefore, timeliness of sending messages by the public cloud server can be maintained through websocket long connection, communication traffic is reduced, and resource consumption is reduced.
S102, sending the message to be sent to the cloud service client of the target node, so that the cloud service client of the target node sends the message to be sent to the private cloud server.
On the basis of S101, this step aims at sending the message to be sent to the cloud service client of the target node, so that the cloud service client of the target node sends the message to be sent to the private cloud server. It can be seen that, by the private cloud server in this step, the message can be sent to the private cloud server without using an exposed interface.
The cloud service client can be directly connected with the private cloud, so that any technical scheme that the cloud service client sends information to the private cloud server can be directly adopted, the information can be sent to the private cloud server through a TCP (Transmission Control Protocol ) protocol, and the information can be sent to the private cloud server through an HTTP (HyperText Transfer Protocol ) protocol. It should be noted that the manner of sending the message in this step is not limited in detail herein.
The number of target nodes in this embodiment may be one or a plurality. Furthermore, in order to maintain the online number of the target nodes and the stability of connection with the public cloud server, the public cloud server may be connected with a plurality of target nodes, and then send the same message to be sent to the plurality of target nodes at the same time, or send different messages to be sent to different target nodes respectively. In order to reduce the performance waste, the public cloud server can be connected with a single target node, and all the messages to be sent are sent to the cloud service client of the target node.
Further, when the number of the target nodes is one, the public cloud server is connected with the cloud service client of the target node through websocket long connection, so that the stability of connection between the public cloud server and the cloud service client of the target node and the effectiveness of data transmission can be kept. When the number of the target nodes is multiple, a great deal of performance resources are required to be consumed for connecting the public cloud server with the multiple target nodes, and the stability of the system is affected.
Further, in order to improve stability of the target node, keep the message to be sent in the public cloud server timely sent to the target node, improve efficiency of message sending, the embodiment may further include:
step 1, selecting a plurality of candidate nodes of the activated clients from a plurality of nodes;
and 2, determining a target node from the candidate nodes of the plurality of activated clients according to the access frequency and the access time.
It can be seen that in this alternative the target node is selected among a plurality of candidate nodes of the activated clients. In the alternative scheme, first, selecting a plurality of alternative nodes of the activated clients from a plurality of nodes; i.e. it is first necessary to keep the client in the node active in order to be able to transmit data via the client. The target node is then determined from the plurality of candidate nodes for the activated clients based on the access frequency and access time. The target node is determined through the access frequency and the access time, and mainly the node with lower access frequency and close access time is selected so as to select the node with higher reliability and sufficient performance as the target node.
Further, in order to improve stability of the target node, when an accident occurs to the target node, the target node can be repaired in time, and this step may further include:
when the cloud service client of the target node is disconnected with the public cloud server, a new node is determined from the plurality of nodes to serve as a new target node, so that the public cloud server is connected with the cloud service client of the new target node.
It can be seen that, in this alternative, when the target node is disconnected, a new node is determined as a new target node, and the public cloud server is directly connected with the new target node, so as to keep that the public cloud server has a corresponding target node in real time, and is used for timely sending a message.
In summary, in this embodiment, the public cloud server is connected with the cloud service client of the target node, and then the message to be sent is sent to the cloud service client of the target node, instead of the public cloud server directly sending the message to the private cloud server, and then the cloud service client of the target node sends the message to be sent to the private cloud server, so that the private cloud server receives the message sent by the public cloud server, instead of exposing the private cloud server interface and then sending the message, the reliability of accessing the private cloud server is maintained, and the security of the private cloud server is improved.
The cloud computing message sending method provided by the application is further described in the following through another embodiment.
Referring to fig. 2, fig. 2 is a flowchart of another cloud computing message sending method according to an embodiment of the present application.
In this embodiment, the process that the cloud service client of the target node sends the message to be sent to the private cloud server in the previous embodiment is mainly optimized, which mainly improves the efficiency of sending the message to the private cloud server, reduces the performance pressure of the target node, and keeps the information forwarding to be effectively performed, where the method may include:
s201, a cloud service client of a target node sends a message to be sent to cloud service clients of other nodes;
the step aims at the cloud service client side which receives the message to be sent to send the message to be sent to cloud service client sides of other nodes.
It can be seen that the other nodes in this step refer to nodes in the same distributed cluster as the target node. The other nodes are not different from the target node from a hardware and software perspective. The number of other nodes may be one or a plurality. When the number of other nodes is one, the cloud service client of the target node directly sends the message to be sent to the other nodes so as to maintain the performance utilization rate and reduce the performance consumption. When the number of other nodes is multiple, the cloud service client of the target node directly transmits the message to be transmitted to the multiple other nodes, so that the nodes all transmit the message to be transmitted to the private cloud server, the message to be transmitted can be effectively transmitted to the private cloud server, the reliability of message transmission is maintained, and the condition of message loss is avoided.
The method for sending the message from the cloud service client of the target node to the cloud service client of the other node may refer to any message sending method provided in the prior art, and is not specifically limited herein.
Optionally, the step may include:
and the cloud service client of the target node sends the message to be sent to the cloud service clients of other nodes through a TCP protocol.
S202, the cloud service clients of other nodes send the received message to be sent to the private cloud server.
On the basis of S101, this step aims at the cloud service client of the other node sending the received message to be sent to the private cloud server. Therefore, the cloud service client of the other nodes receiving the message to be sent in the step directly sends the message to be sent to the private cloud server, and the message to be sent is sent to the private cloud server without exposing the private cloud server, so that data in the private cloud server is prevented from being stolen.
Optionally, the present embodiment may further include:
when the message sending to the cloud service client of the other node fails, the cloud service client of the target node sends the message to be sent to the cloud service client of the next other node.
It can be seen that the present alternative mainly describes the case where the message transmission fails. When the message transmission fails, the cloud service client of the target node directly transmits the message to be transmitted to the cloud service client of the next other node so as to transmit the message to be transmitted in time.
It can be seen that, in this embodiment, the message to be sent is sent to the cloud service client of the other node through the cloud service client of the target node, and then the cloud service client of the other node resends the received message to be sent to the private cloud server, instead of directly sending the message to the private cloud server, so that the cloud service client of the target node is prevented from sending too much message data in a short time, and the performance utilization rate is improved.
The cloud computing message sending method provided by the application is further described through another specific embodiment.
In this embodiment, the communication node is the target node mentioned above, and the method may include:
first, when a client uses a cloud service client, the cloud service client registers in a node container of public cloud, and selects a node as a communication node according to access frequency and time, and connects with the cloud service client of the communication node.
Then, the communication node and the public cloud server are connected in a long mode through websocket to maintain a connection state, and cloud service clients of other nodes only need to keep communication with the communication node. When the communication node is deactivated or disconnected, the communication node can be selected from a plurality of points again, so long as one cloud service client is in an active state. In addition to the communication nodes, cloud service clients of other nodes can all carry out carrier tools for message distribution. That is, the communication node sends the message to the cloud service client of the other node, and then sends the message to the private cloud server through the cloud service client of the other node. If the message of a certain node fails to be sent, the message can be forwarded to the next node to be sent by the communication node, so that the network abnormality of the client environment of the partial cloud service is avoided.
And finally, the private cloud server can receive the message sent by the public cloud server through the communication node or other nodes, so that the data of the private cloud server are prevented from being exposed to the outside, and the data security of the private cloud server is improved.
In this embodiment, websocket is used as a long connection technology of a public cloud server and a communication node, and compared with other long polling technologies, instant pushing of a server can be achieved, traffic is reduced, and resource consumption is reduced.
It can be seen that, in this embodiment, the public cloud server is connected with the cloud service client of the target node, and then the message to be sent is sent to the cloud service client of the target node, instead of the public cloud server directly sending the message to the private cloud server, and then the cloud service client of the target node sends the message to be sent to the private cloud server, so that the private cloud server receives the message sent by the public cloud server, instead of exposing the private cloud server interface and then sending the message, the reliability of accessing the private cloud server is maintained, and the security of the private cloud server is improved.
The following describes a cloud computing message sending device provided by an embodiment of the present application, where the cloud computing message sending device described below and the cloud computing message sending method described above may be referred to correspondingly.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a cloud computing message sending device according to an embodiment of the present application.
In this embodiment, the apparatus may include:
the client connection module 100 is configured to connect with a cloud service client of the target node; the target node is a node determined from a plurality of nodes according to the node state information and the client state information;
the message sending module 200 is configured to send a message to be sent to a cloud service client of the target node, so that the cloud service client of the target node sends the message to be sent to the private cloud server.
Optionally, the apparatus may further include:
the target node determining module is used for selecting a plurality of candidate nodes of the activated clients from a plurality of nodes; the target node is determined from the plurality of candidate nodes of the activated clients according to the access frequency and the access time.
Optionally, the apparatus may further include:
and the target node reselection module is used for determining a new node from the plurality of nodes as a new target node when the cloud service client of the target node is disconnected with the public cloud server, so that the public cloud server is connected with the cloud service client of the new target node.
Optionally, the target node may be configured to send the message to be sent to a cloud service client of the other node;
alternatively, other nodes may be used to send the received message to be sent to the private cloud server.
Optionally, the apparatus may further include:
and the node resending module is used for sending the message to be sent to the cloud service client of the next other node when the message sending to the cloud service client of the other node fails.
Alternatively, the client connection module 100 may be configured to connect with a cloud service client of the target node through a websocket long connection.
Referring to fig. 4, fig. 4 is a schematic structural diagram of another cloud computing messaging device according to an embodiment of the present application, where the cloud computing messaging device may have a relatively large difference due to different configurations or performances, and may include one or more processors (central processing units, CPU) 622 (e.g., one or more processors) and a memory 632, and one or more storage media 630 (e.g., one or more mass storage devices) storing application programs 642 or data 644. Wherein memory 632 and storage medium 630 may be transitory or persistent storage. The program stored on the storage medium 630 may include one or more modules (not shown), each of which may include a series of instruction operations in a computing device. Still further, the central processor 622 may be configured to communicate with a storage medium 630 to execute a series of instruction operations in the storage medium 630 on the computing device 600.
The control device 600 may also include one or more power supplies 626, one or more wired or wireless network interfaces 650, one or more input/output interfaces 658, and/or one or more operating systems 641, such as Windows ServerTM, mac OS XTM, unixTM, linuxTM, freeBSDTM, and the like.
The steps in the cloud computing message sending method described in fig. 1 to 2 are implemented by a cloud computing message sending method based on the structure shown in fig. 4.
Referring to fig. 5, fig. 5 is a schematic structural diagram of a server according to an embodiment of the present application.
The embodiment of the application also provides a server, which comprises:
a memory 11 for storing a computer program;
a processor 12 for implementing the steps of the cloud computing messaging method as described in the above embodiments when executing the computer program.
The embodiment of the application also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the steps of the cloud computing message sending method according to the above embodiment.
It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.
In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of elements is merely a logical functional division, and there may be additional divisions of actual implementation, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in whole or in part in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a function calling device, or a network device, etc.) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The cloud computing message sending method, the cloud computing message sending device, the server and the computer readable storage medium provided by the application are described in detail. The principles and embodiments of the present application have been described herein with reference to specific examples, the description of which is intended only to facilitate an understanding of the method of the present application and its core ideas. It should be noted that it will be apparent to those skilled in the art that various modifications and adaptations of the application can be made without departing from the principles of the application and these modifications and adaptations are intended to be within the scope of the application as defined in the following claims.

Claims (10)

1. A cloud computing message sending method, comprising:
the public cloud server is connected with a cloud service client of the target node; the target node is a node determined from a plurality of nodes according to node state information and client state information; the cloud service client of the target node is a client program for providing services for users by cloud service;
and sending the message to be sent to the cloud service client of the target node, so that the cloud service client of the target node sends the message to be sent to a private cloud server.
2. The cloud computing message transmission method of claim 1, further comprising:
selecting a plurality of candidate nodes of the activated clients from the plurality of nodes;
and determining the target node from the candidate nodes of the plurality of activated clients according to the access frequency and the access time.
3. The cloud computing message transmission method of claim 1, further comprising:
and when the cloud service client of the target node is disconnected with the public cloud server, determining a new node from the plurality of nodes as a new target node so that the public cloud server is connected with the cloud service client of the new target node.
4. A cloud computing message transmission method according to any of claims 1 to 3, characterized in that the step of the cloud service client of the target node transmitting the message to be transmitted to a private cloud server comprises:
the cloud service client of the target node sends the message to be sent to cloud service clients of other nodes;
and the cloud service clients of the other nodes send the received message to be sent to the private cloud server.
5. The cloud computing messaging method of claim 4, further comprising:
and when the message sending to the cloud service client of the other node fails, the cloud service client of the target node sends the message to be sent to the cloud service client of the next other node.
6. The cloud computing message transmission method according to claim 5, wherein the connection between the public cloud server and the cloud service client of the target node includes:
and the public cloud server is connected with the cloud service client of the target node through websocket long connection.
7. The cloud computing message transmission method according to claim 6, wherein the cloud service client of the target node transmits the message to be transmitted to cloud service clients of other nodes, comprising:
and the cloud service client of the target node sends the message to be sent to cloud service clients of other nodes through a TCP protocol.
8. A cloud computing message transmitting apparatus, comprising:
the client connection module is used for connecting with a cloud service client of the target node; the target node is a node determined from a plurality of nodes according to node state information and client state information; the cloud service client of the target node is a client program for providing services for users by cloud service;
and the message sending module is used for sending the message to be sent to the cloud service client of the target node so that the cloud service client of the target node sends the message to be sent to the private cloud server.
9. A server, comprising:
a memory for storing a computer program;
a processor for implementing the steps of the cloud computing messaging method according to any of claims 1 to 7 when executing the computer program.
10. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the cloud computing messaging method according to any of claims 1 to 7.
CN202011305674.4A 2020-11-19 2020-11-19 Cloud computing message sending method and related device Active CN112272241B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011305674.4A CN112272241B (en) 2020-11-19 2020-11-19 Cloud computing message sending method and related device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011305674.4A CN112272241B (en) 2020-11-19 2020-11-19 Cloud computing message sending method and related device

Publications (2)

Publication Number Publication Date
CN112272241A CN112272241A (en) 2021-01-26
CN112272241B true CN112272241B (en) 2023-09-19

Family

ID=74340363

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011305674.4A Active CN112272241B (en) 2020-11-19 2020-11-19 Cloud computing message sending method and related device

Country Status (1)

Country Link
CN (1) CN112272241B (en)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110430281A (en) * 2019-08-15 2019-11-08 深圳市般若大数据技术有限公司 Method, apparatus, equipment and the storage medium of public cloud acquisition private clound data
CN111385203A (en) * 2020-03-19 2020-07-07 上海东普信息科技有限公司 Data transmission method, device and equipment based on hybrid cloud and storage medium

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9137222B2 (en) * 2012-10-31 2015-09-15 Vmware, Inc. Crypto proxy for cloud storage services
US10484460B2 (en) * 2016-07-22 2019-11-19 Microsoft Technology Licensing, Llc Access services in hybrid cloud computing systems

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110430281A (en) * 2019-08-15 2019-11-08 深圳市般若大数据技术有限公司 Method, apparatus, equipment and the storage medium of public cloud acquisition private clound data
CN111385203A (en) * 2020-03-19 2020-07-07 上海东普信息科技有限公司 Data transmission method, device and equipment based on hybrid cloud and storage medium

Also Published As

Publication number Publication date
CN112272241A (en) 2021-01-26

Similar Documents

Publication Publication Date Title
CN112799789B (en) Node cluster management method, device, equipment and storage medium
CN102546794B (en) Method for directly communicating browser client with back-end server as well as gateway and communication system
CN101253488B (en) Distributed caching of files in a network
EP2699024B1 (en) Near Field Communication Device
US8001176B2 (en) Web service with multiple listening endpoints
RU2009138333A (en) SETTING A SAMPLE PHASE CONNECTION
CN110808948B (en) Remote procedure calling method, device and system
EP2699023B1 (en) Near Field Communication Device
CN108418903B (en) Remote access system and access method for embedded software log
Srirama et al. Scalable mobile web services mediation framework
CN111857772B (en) Method and device for remote transmission and dynamic loading of terminal edge application program
Aldmour et al. An approach for offloading in mobile cloud computing to optimize power consumption and processing time
US11463549B2 (en) Facilitating inter-proxy communication via an existing protocol
CN112272241B (en) Cloud computing message sending method and related device
JP6988973B2 (en) System processing using OPC UA, communication method using OPC UA, and load balancer
WO2011150968A1 (en) Communication method and device
CN112422609A (en) Programming device and service request connection method
CN115378989B (en) MQTT theme subscription system, method, terminal and medium based on wake-up channel
CN106411588A (en) Network device management method, master device and management server
US20040066770A1 (en) Method for communicating with a resource-constrained device on an edge of a network
CN112995311B (en) Service providing method, device and storage medium
CN113691510A (en) Cross-domain access control method, system, storage medium and equipment
CN111490997B (en) Task processing method, proxy system, service system and electronic equipment
EP3796598A1 (en) Node switching method, network node, network system, and storage medium
CN110392017B (en) Method and related device for processing RPC message

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