CN112260888A - Container cloud and resource management method of container cloud - Google Patents
Container cloud and resource management method of container cloud Download PDFInfo
- Publication number
- CN112260888A CN112260888A CN202011031012.2A CN202011031012A CN112260888A CN 112260888 A CN112260888 A CN 112260888A CN 202011031012 A CN202011031012 A CN 202011031012A CN 112260888 A CN112260888 A CN 112260888A
- Authority
- CN
- China
- Prior art keywords
- client
- resource management
- management server
- information
- server
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
- H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
-
- 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/08—Configuration management of networks or network elements
- H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L43/00—Arrangements for monitoring or testing data switching networks
- H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
- H04L43/106—Active monitoring, e.g. heartbeat, ping or trace-route using time related information in packets, e.g. by adding timestamps
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Cardiology (AREA)
- General Health & Medical Sciences (AREA)
- Environmental & Geological Engineering (AREA)
- Computer And Data Communications (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to a container cloud and a resource management method of the container cloud, wherein the method comprises the following steps: when the state detection server receives heartbeat information sent by a client, initializing timing time and starting timing; when the timing time is longer than the expiration time and the heartbeat information sent again by the client is not received, client off-line information is generated and pushed to the resource management server; and the resource management server recovers the resources allocated to the client based on the received client offline information. Tasks in the container cloud for detecting whether the client is still online are assigned to the status detection server and are no longer performed by the resource management server. By adding the state detection server, the load of the resource management server is correspondingly reduced, the resource management server can be concentrated on the container cloud resource allocation task, and the stable performance of the resource management server is ensured.
Description
Technical Field
The application relates to the technical field of cloud services, in particular to a container cloud and a resource management method of the container cloud.
Background
Because the cloud server has the advantages of rapid deployment, upgrading and maintenance, more and more clients adopt the container cloud deployment server at present; accordingly, the number of customers that the container cloud needs to support is increasing. In order to ensure effective utilization of container cloud resources, after a certain client is offline, resources configured for the client can be quickly recovered, and the container cloud also needs to monitor the online state of the client.
In the prior art, in order to monitor the online state of a client, a resource management server of a container cloud initiates an online state detection message to the client in a polling manner, and when a corresponding message returned by the client is not received within a time threshold, it is determined that the client is offline and corresponding resources are recovered. However, as the number of clients increases rapidly, the active probing pressure of the resource management server increases, and the stability thereof also decreases.
Disclosure of Invention
In order to solve the technical problems or at least partially solve the technical problems, the application provides a container cloud resource management method and device.
In one aspect, the application provides a container cloud resource management method, which is applied to a container cloud comprising a state detection server and a resource management server; the method comprises the following steps:
when the state detection server receives heartbeat information sent by a client, initializing timing time and starting timing; and the number of the first and second groups,
generating client side offline information under the condition that the timing time is longer than the expiration time and the heartbeat information sent again by the client side is not received, and pushing the client side offline information to the resource management server;
and the resource management server recovers the resources allocated to the client based on the received client offline information.
Optionally, the heartbeat information includes a transmission timestamp;
the initializing the timing time to start timing includes: and initializing the timing time and starting timing by taking the time point of the sending timestamp as a starting point.
Optionally, the heartbeat information further includes a set timing time;
and the state detection server takes the set timing time as the expiration time.
Optionally, the container cloud resource management method further includes:
the state detection server receives heartbeat information sent by a client, generates client online information under the condition that the client is determined to be a new online client according to the heartbeat information, and pushes the client online information to the resource management server;
and the resource management server allocates resources for the new online client based on the received online information of the client.
Optionally, the pushing the client offline information to the resource management server includes:
and sending the client offline message to an asynchronous message queue of the resource management server, and pushing the client offline message to the resource management server.
In another aspect, the present application provides a container cloud comprising a state detection server and a resource management server;
the state detection server is used for initializing timing time and starting timing when receiving heartbeat information sent by the client; when the timing time is longer than the expiration time and the heartbeat information sent again by the client is not received, client off-line information is generated and pushed to the resource management server;
and the resource management server is used for recovering the resources distributed to the client based on the received client offline information.
Optionally, the heartbeat information includes a transmission timestamp; and the state detection server initializes the timing time and starts timing by taking the time point of the sending timestamp as a starting point.
Optionally, the heartbeat information further includes a set timing time;
and the state detection server takes the set timing time as the expiration time.
Optionally, the state detection server generates client online information when receiving heartbeat information sent by a client and determining that the client is a new online client according to the heartbeat information, and pushes the client online information to the resource management server;
and the resource management server is also used for distributing resources for the new online client based on the received online information of the client.
Optionally, the state detection server pushes the client offline information to the resource management server, specifically:
and sending the client offline message to an asynchronous message queue of the resource management server, and pushing the client offline message to the resource management server.
In the container cloud and the container cloud resource management method provided by the application, a task for detecting whether a client is still online in the container cloud is allocated to a state detection server and is not executed by a resource management server any more. By adding the state detection server, the load of the resource management server is correspondingly reduced, the resource management server can be concentrated on the container cloud resource allocation task, and the stable performance of the resource management server is ensured.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art to obtain other drawings without inventive exercise.
Fig. 1 is a schematic structural diagram of a container cloud system provided in an embodiment of the present application;
fig. 2 is a flowchart of a container cloud resource management method provided in an embodiment of the present application;
FIG. 3 is a flowchart for triggering a resource management server to allocate resources to a client according to an embodiment of the present application;
wherein: 01-client, 11-state detection server, 12-resource management server, 13-task server.
Detailed Description
In order that the above-mentioned objects, features and advantages of the present application may be more clearly understood, the solution of the present application will be further described below. It should be noted that the embodiments and features of the embodiments of the present application may be combined with each other without conflict.
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application, but the present application may be practiced in other ways than those described herein; it is to be understood that the embodiments described in this specification are only some embodiments of the present application and not all embodiments. The embodiment of the application provides a management method of container cloud resources, which is used for enabling a container cloud to determine a disconnected client and then releasing resources allocated to the client.
Fig. 1 is a schematic structural diagram of a container cloud system provided in an embodiment of the present application. As shown in fig. 1, a container cloud system provided in an embodiment of the present application includes a container cloud and a client; the container cloud includes a state detection server 11, a resource management server 12, and a task server 13 for actually providing cloud services.
In this embodiment of the application, the client 01 may be connected to the status detection server 11 to send heartbeat information to the status detection server 11; the client 01 may also establish a connection with the task server 13 that actually provides cloud service resources to transmit traffic data.
Fig. 2 is a flowchart of a container cloud resource management method provided in an embodiment of the present application. As shown in fig. 2, the container cloud resource management method provided in the embodiment of the present application includes steps S101 to S103.
Wherein, steps S101 and S102 are executed by the status detection server, and step S103 is executed by the resource management server.
S101: when heartbeat information sent by a client is received, a timing time is initialized and timing is started.
In the embodiment of the application, the client can send heartbeat information to the state detection server after being on line. In specific application, the client can adopt a keep-alive interface https:// ip: port/keepalive provided by Restful API to send heartbeat information to the state detection server so as to inform the state detection server that the state detection server is still in an online state.
In this embodiment of the present application, the heartbeat information sent by the client at least includes an identity that uniquely represents the client, and the identity may be determined by using information such as a MAC address of the client.
After receiving heartbeat information sent by a client, a state detection server determines that the client is still in an online state according to an identity in the heartbeat information, so that the client initializes timing time and starts timing; the timer time is an accumulation time, is set to 0 after initialization thereof, and starts accumulation again.
S102: and generating client side offline information under the condition that the heartbeat information sent again by the client side is not received when the timing time exceeds the expiration time, and pushing the client side offline information to the resource management server.
The expiration time set in the status detection server is a threshold time for determining whether the client is offline. After the state server initializes the timing time to start timing, and the timing time exceeds the expiration time but does not receive the information sent again by the client, the state server determines that the client is offline; and then the state detection server generates client offline information corresponding to the client based on the judgment that the client is offline. It should be noted that the client offline information includes an identification of the client that is deemed to have been offline.
In the embodiment of the application, the mode of sending the client offline information by the state detection server can be provided for the resource management server in the form of subscription service. And after the resource management server subscribes to the corresponding theme, the state detection server determines the address of the resource management server. And after generating new client offline information, the state detection server sends the client offline information to the resource management server.
In this embodiment, the resource management server may set an asynchronous message queue, and the state detection server may send the client offline message to the asynchronous message queue of the resource management server, and push the client offline message to the resource management server. In this way, the resource management server can call the messages in the asynchronous message queue according to the task state of the resource management server, and process the messages one by one.
S103: and recovering the resources allocated to the client based on the received client offline information.
After receiving the client offline information, the resource management server determines that the client is offline according to the client identifier, so that resources allocated to the client are recovered to avoid long-term invalid occupation of the resources.
In the embodiment of the application, the task for detecting whether the client is still online in the container cloud is allocated to the state detection server and is not executed by the resource management server any more. By adding the state detection server, the load of the resource management server is correspondingly reduced, the resource management server can be concentrated on the container cloud resource allocation task, and the stable performance of the resource management server is ensured.
In the container cloud system provided by one application of the embodiment of the application, a client can be configured with a functional module for actively sending heartbeat information to a state detection server; and after the client is on line and is connected with the container cloud, actively sending heartbeat information to the state detection server.
In a specific application of the embodiment of the present application, the heartbeat information sent by the client may include a sending time stamp. The transmission time stamp is an identifier for indicating the time when the client transmits the heartbeat information. Correspondingly, after receiving the heartbeat information, the state detection server may start timing by using the sending timestamp therein as a timing starting point, and determine that the client has been offline when the timing time is greater than the expiration time.
Because the sending time stamp provided by the client is used as the timing starting point, and the time point of receiving the heartbeat information is not used as the timing starting point, the time consumption generated in the network transmission process of the heartbeat information is put in the timing time, so that the judgment on whether the client is off-line or not is more timely. Because the judgment on whether the client is offline is more timely, the client offline information is generated more timely, and the resource management server can recover the resources allocated to the client by the server earlier, so that the resource utilization rate is improved.
In other applications of the embodiment of the present application, the heartbeat information sent by the client may not include the sending timestamp. Correspondingly, the state detection server starts timing with the time point of receiving the heartbeat information as a starting point.
In a specific application of the embodiment of the present application, the heartbeat information may further include a set timing time. The set timing time is set by the client and is used for informing the state detection server of the time for setting the expiration time characteristic. The client can appoint timing time according to the type, the network state and the priority of the task. After receiving the heartbeat information, the state detection server may use a set timing time therein as an expiration time.
In another application, the state detection server may further store a data table used for determining how to set the timing time of the client, such as the priority level of the client and the task type of the client, so as to set the expiration time according to the priority level of the client and the task type of the client in the data table. In other applications, the status detection server may also set a default expiration time for each client.
In a specific application of the embodiment of the present application, the state detection server may be further configured to trigger the resource management server to allocate resources to the client after the client is online. Fig. 3 is a flowchart for triggering a resource management server to allocate resources to a client according to an embodiment of the present application.
As shown in fig. 3, the step of the state detection server triggering the allocation of resources to the client comprises S201-S204.
S201: and receiving heartbeat information sent by the client, and extracting the identity.
In order to realize the function that the state detection server distributes resources for the client, the client is configured to send heartbeat information to the state detection server after the online initialization is completed; and after receiving the heartbeat information, the state detection server extracts the identity identification in the heartbeat information.
S202: determining whether the client is in a state list of the client according to the identity; if not, S203 is executed.
S203: and determining the client as a new online client, generating online information of the client, and sending the online information of the client to the resource server.
And under the condition that the client is not in the own state list, the client is determined as a new online client. The state detection server generates client on-line information immediately and sends the client on-line information to the resource management server.
S204: and allocating resources for the client based on the received online information of the client.
After receiving the client online information, the resource management server allocates resources for the newly online client; and then the task server where the resource is allocated establishes connection with the new online client to provide service for the client.
The resource management server may only handle resource allocation and reclamation tasks, as it may be dedicated by the status detection server to determine the client's online and offline.
In other applications of the embodiment of the present application, after the initialization is completed, the client may also directly send the client online information to the resource management server, and directly allocate resources by the resource management server. In this case, the state detection server may start the initialization timing by receiving heartbeat information transmitted from the client, or may start the initialization timing by receiving information on allocated resources transmitted from the resource management server.
Besides providing the foregoing container cloud resource management method, an embodiment of the present application also provides a container cloud.
As shown in fig. 1, the container cloud provided in the embodiment of the present application includes a state detection server 11 and a resource management server 12, and further includes a task server 13 for actually providing a service for a client 01.
The state detection server 11 and the client 01 are at least in one-way communication connection to receive the heartbeat information sent by the client 01. The state detection server 11 is configured to initialize a timing time and start timing when receiving heartbeat information sent by the client 01; and under the condition that the timing time is more than the expiration time and the heartbeat information sent again by the client 01 is not received, generating client off-line information and pushing the client off-line information to the resource management server 12.
After receiving heartbeat information sent by the client 01, the state detection server 11 determines that the client 01 is still in an online state according to identity representation in the heartbeat information, so that the client 01 initializes timing time and starts timing; the timer time is an accumulation time, is set to 0 after initialization thereof, and starts accumulation again.
After the state server initializes the timing time to start timing, and the timing time exceeds the expiration time but does not receive the information sent again by the client 01, the state server determines that the client 01 is offline; then, the status detection server 11 generates client offline information corresponding to the client 01 based on the determination that the client 01 has been offline. It should be noted that the client offline information includes an identification of client 01 that is deemed to have been offline.
In the embodiment of the present application, the manner in which the status detection server 11 sends the client offline information may be provided to the resource management server 12 in the form of a subscription service. After the resource management server 12 subscribes to the corresponding topic, the status detection server 11 determines the address of the resource management server 12. After generating the new client offline information, the status detection server 11 sends the client offline information to the resource management server 12.
In this embodiment, the status detection server 11 may send the client offline information to the asynchronous message queue of the resource management server 12, and push the client offline information to the resource management server 12. In this way, the resource management server 12 can call the messages in the asynchronous message queue according to the task state thereof, and process the corresponding tasks one by one.
The resource management server 12 is configured to recover the resources allocated to the server based on the received client offline information. After receiving the client offline information, the resource management server 12 determines that the client 01 has been offline according to the client 01 identifier therein, so that the resources allocated to the client 01 are recovered to avoid long-term invalid occupation of the resources.
In the embodiment of the present application, the task in the container cloud for detecting whether the client 01 is still online is allocated to the status detection server 11, and is no longer executed by the resource management server 12. By adding the state detection server 11, the load of the resource management server 12 is correspondingly reduced, the resource management server can be concentrated on the container cloud resource allocation task, and the stable performance of the resource management server 12 is ensured.
In one particular application, the heartbeat information sent by client 01 may include a send timestamp. Upon receiving the heartbeat information, the state detection server 11 extracts the transmission time in the heartbeat information as a start point of the time measurement, initializes the time measurement time, and starts the time measurement.
Because the sending timestamp provided by the client 01 is used as the timing starting point, and the time point of receiving the heartbeat information is not used as the timing starting point, the time consumption generated by the heartbeat information in the network transmission process is put in the timing time, so that the judgment on whether the client 01 is offline is more timely. Because the judgment on whether the client 01 is offline is more timely, the client offline information is generated more timely, and the resource management server 12 can also recover the resources allocated by the server to the client 01 earlier, so that the resource utilization rate is improved.
In an application of this embodiment, the heartbeat information sent by the client 01 may further include a set timing time. After receiving the heartbeat information, the status detection server 11 takes the set timing time therein as the expiration time.
In another application, the status detection server 11 may further store a data table used by the priority level of the client 01, the task type of the client 01, and the like to determine how to set the timing time of the client 01, so as to set the expiration time according to the priority level of the client 01 and the task type of the client 01 in the data table.
In another specific application of the embodiment of the present application, the status detection server 11 may be further configured to trigger the resource management server 12 to allocate resources to the client 01. Specifically, the client 01 is configured to send heartbeat information to the state detection server 11 after the online initialization is completed; after receiving the heartbeat information, the status detection server 11 extracts the identifier thereof to determine that the client 01 is not in the status list of the client 01, and determines that the client 01 is a new online client 01.
The status detection server 11 then generates client online information and sends the client online information to the resource management server 12. After receiving the client online information, the resource management server 12 allocates resources to the newly online client 01. The task server 13 where the resource is allocated establishes a connection with the new online client 01 to provide a service to the client 01.
In other applications of the embodiment of the present application, after the initialization is completed, the client 01 may also directly send the client online information to the resource management server 12, and directly allocate resources by the resource management server 12. In this case, the state detection server 11 may start the initialization timing by receiving the heartbeat information transmitted from the client 01, or may start the initialization timing by receiving the information on the allocated resources transmitted from the resource management server 12.
The embodiments of the present application further provide a non-transitory computer-readable storage medium, where the non-transitory computer-readable storage medium stores a program or an instruction, and the program or the instruction enables a computer to execute the steps of the embodiments of the method for managing cloud resources of a container, which are not described herein again to avoid repeated descriptions.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
The above description is merely exemplary of the present application and is presented to enable those skilled in the art to understand and practice the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.
Claims (10)
1. A container cloud resource management method is characterized by being applied to a container cloud comprising a state detection server and a resource management server; the method comprises the following steps:
when the state detection server receives heartbeat information sent by a client, initializing timing time and starting timing; and the number of the first and second groups,
generating client side offline information under the condition that the timing time is longer than the expiration time and the heartbeat information sent again by the client side is not received, and pushing the client side offline information to the resource management server;
and the resource management server recovers the resources allocated to the client based on the received client offline information.
2. The container cloud resource management method of claim 1, wherein the heartbeat information includes a send timestamp;
the initializing the timing time to start timing includes: and initializing the timing time and starting timing by taking the time point of the sending timestamp as a starting point.
3. The container cloud resource management method according to claim 2, wherein the heartbeat information further includes a set timing time;
and the state detection server takes the set timing time as the expiration time.
4. The container cloud resource management method according to any one of claims 1 to 3, further comprising:
the state detection server receives heartbeat information sent by a client, generates client online information under the condition that the client is determined to be a new online client according to the heartbeat information, and pushes the client online information to the resource management server;
and the resource management server allocates resources for the new online client based on the received online information of the client.
5. The container cloud resource management method according to any one of claims 1 to 3, wherein the pushing the client offline information to the resource management server includes:
and sending the client offline message to an asynchronous message queue of the resource management server, and pushing the client offline message to the resource management server.
6. A container cloud comprising a state detection server and a resource management server;
the state detection server is used for initializing timing time and starting timing when receiving heartbeat information sent by the client; when the timing time is longer than the expiration time and the heartbeat information sent again by the client is not received, client off-line information is generated and pushed to the resource management server;
and the resource management server is used for recovering the resources distributed to the client based on the received client offline information.
7. The container cloud of claim 6, wherein:
the heartbeat information includes a transmission timestamp; and the state detection server initializes the timing time and starts timing by taking the time point of the sending timestamp as a starting point.
8. The container cloud of claim 7, wherein the heartbeat information further includes a set timing time;
and the state detection server takes the set timing time as the expiration time.
9. The container cloud according to any of claims 6-8, wherein:
the state detection server receives heartbeat information sent by a client, generates client online information under the condition that the client is determined to be a new online client according to the heartbeat information, and pushes the client online information to the resource management server;
and the resource management server is also used for distributing resources for the new online client based on the received online information of the client.
10. The container cloud according to any of claims 6-8, wherein:
the state detection server pushes the client offline information to the resource management server, specifically:
and sending the client offline message to an asynchronous message queue of the resource management server, and pushing the client offline message to the resource management server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011031012.2A CN112260888B (en) | 2020-09-27 | 2020-09-27 | Container cloud and resource management method of container cloud |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011031012.2A CN112260888B (en) | 2020-09-27 | 2020-09-27 | Container cloud and resource management method of container cloud |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112260888A true CN112260888A (en) | 2021-01-22 |
| CN112260888B CN112260888B (en) | 2022-07-12 |
Family
ID=74233820
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011031012.2A Active CN112260888B (en) | 2020-09-27 | 2020-09-27 | Container cloud and resource management method of container cloud |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112260888B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114198886A (en) * | 2021-12-15 | 2022-03-18 | 珠海格力电器股份有限公司 | Method and device for calculating power-off time of equipment and equipment |
| CN115022393A (en) * | 2022-05-11 | 2022-09-06 | 杭州网易云音乐科技有限公司 | Method, apparatus, medium, and computing device for determining connection status |
| CN115277827A (en) * | 2022-07-26 | 2022-11-01 | 中国电信股份有限公司 | Cloud resource configuration method, system, device, equipment and storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102647314A (en) * | 2012-05-16 | 2012-08-22 | 深圳市乐唯科技开发有限公司 | Client side on-line state judgment method and system |
| CN103491102A (en) * | 2013-09-30 | 2014-01-01 | 天脉聚源(北京)传媒科技有限公司 | Method, system and device for monitoring stability of internet audio and video |
| CN103546510A (en) * | 2012-07-13 | 2014-01-29 | 云联（北京）信息技术有限公司 | Management system and management method on basis of cloud service |
| CN104125569A (en) * | 2013-04-28 | 2014-10-29 | 中兴通讯股份有限公司 | Communication management method and communication system |
| CN105933199A (en) * | 2016-04-08 | 2016-09-07 | 武汉斗鱼网络科技有限公司 | Method for maintaining heartbeat connection, gateway and chat server |
| CN106922039A (en) * | 2015-12-25 | 2017-07-04 | 阿里巴巴集团控股有限公司 | The sending method and device of a kind of heartbeat message |
| CN109905259A (en) * | 2017-12-08 | 2019-06-18 | 中国电信股份有限公司 | Communicate to connect maintenance method, system and relevant device |
-
2020
- 2020-09-27 CN CN202011031012.2A patent/CN112260888B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102647314A (en) * | 2012-05-16 | 2012-08-22 | 深圳市乐唯科技开发有限公司 | Client side on-line state judgment method and system |
| CN103546510A (en) * | 2012-07-13 | 2014-01-29 | 云联（北京）信息技术有限公司 | Management system and management method on basis of cloud service |
| CN104125569A (en) * | 2013-04-28 | 2014-10-29 | 中兴通讯股份有限公司 | Communication management method and communication system |
| US9716719B2 (en) * | 2013-04-28 | 2017-07-25 | Zte Corporation | Communication managing method and communication system |
| CN103491102A (en) * | 2013-09-30 | 2014-01-01 | 天脉聚源(北京)传媒科技有限公司 | Method, system and device for monitoring stability of internet audio and video |
| CN106922039A (en) * | 2015-12-25 | 2017-07-04 | 阿里巴巴集团控股有限公司 | The sending method and device of a kind of heartbeat message |
| CN105933199A (en) * | 2016-04-08 | 2016-09-07 | 武汉斗鱼网络科技有限公司 | Method for maintaining heartbeat connection, gateway and chat server |
| CN109905259A (en) * | 2017-12-08 | 2019-06-18 | 中国电信股份有限公司 | Communicate to connect maintenance method, system and relevant device |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114198886A (en) * | 2021-12-15 | 2022-03-18 | 珠海格力电器股份有限公司 | Method and device for calculating power-off time of equipment and equipment |
| CN115022393A (en) * | 2022-05-11 | 2022-09-06 | 杭州网易云音乐科技有限公司 | Method, apparatus, medium, and computing device for determining connection status |
| CN115022393B (en) * | 2022-05-11 | 2024-05-17 | 杭州网易云音乐科技有限公司 | Method, device, medium and computing equipment for determining connection state |
| CN115277827A (en) * | 2022-07-26 | 2022-11-01 | 中国电信股份有限公司 | Cloud resource configuration method, system, device, equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112260888B (en) | 2022-07-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112260888B (en) | Container cloud and resource management method of container cloud | |
| EP3648401A1 (en) | Method, device, and computer readable storage medium for managing network slice | |
| CN101068208B (en) | Method, system and proxy equipment for dynamic distributing network address | |
| CN111615066A (en) | Distributed micro-service registration and calling method based on broadcast | |
| CN101656764A (en) | Method, system and device for keeping session of DHCP user active | |
| CN107528891B (en) | Websocket-based automatic clustering method and system | |
| CN113206877A (en) | Session keeping method and device | |
| CN107979539A (en) | Message processing method and device | |
| CN109040295A (en) | Determination method and device, terminal and the storage medium of abnormal broken line | |
| CN104009961B (en) | A kind of pppoe session mark distributing method and equipment | |
| US20140201376A1 (en) | Method and system for the handling of redundant long poll | |
| CN111274022A (en) | Server resource allocation method and system | |
| CN106067857B (en) | Method and device for preventing user from being forced off-line | |
| CN102523316A (en) | Address distribution method and address distribution device | |
| CN103312586A (en) | instant communication | |
| CN112613919A (en) | Information processing method and related device | |
| CN108781215B (en) | Network service implementation method, service controller and communication system | |
| CN101150526B (en) | A method and server for realizing load balance service of dynamic host configuration protocol | |
| CN107273047B (en) | Cache management method, cache manager and storage management software | |
| CN115499414A (en) | Address allocation method and device | |
| CN113687962A (en) | Request processing method, device, equipment and storage medium | |
| WO2014100964A1 (en) | Resource request method, server and resource allocation system | |
| CN110209474B (en) | Task processing method and device | |
| CN112689008A (en) | Network connection pool management method, device, equipment and storage medium | |
| CN112911026A (en) | Address application method, device and equipment |
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 |