TW201602796A - Uninterruptible cloud service system and method - Google Patents

Abstract

An uninterruptible cloud service system includes a cloud server configured for providing a cloud service to process transaction requests and a monitoring server connected to the cloud server and configured for receiving the transaction requests from a client device. The monitoring server includes the following components: an application service core module, a temporary transaction database, a server health check module, and a dispatcher module. The server health check module detects at least one state related to the cloud server. When the states are normal, the dispatcher module sends the transaction requests to the cloud server. When any of the states is abnormal, it sends the transaction requests to the application service core module configured for providing a local service associated with the cloud service to process the transaction requests and storing transaction information generated during processing the transaction requests in the temporary transaction database.

Description

Cloud service continuous line system and method

The present disclosure relates to a system and method for providing cloud services, and more particularly to a system and method for providing continuous cloud services.

Cloud services are a way to provide services based on the Internet. Users no longer need to know the details of the infrastructure in the "cloud", they don't need to have the corresponding expertise, and they don't need to have direct control. They only need to have networking capabilities to access the cloud through browsers, desktop applications or mobile applications. The service and information, the service provider maintains the infrastructure and platform to maintain the normal operation of the service.

The cloud mode allows users to use the services provided by any network-capable device anytime and anywhere, and allows multiple people to share resources and reduce the processing load of the user terminal. Therefore, as the network becomes more and more popular, Road storage, cloud file image processing to cloud calendars, etc. Cloud services for individual users are also more diverse, and more and more enterprise users use cloud services to complete the internal management, operation and even production processes.

The benefit of using cloud services is that companies can deploy more quickly. Use programs and reduce management complexity and maintenance costs, and allow rapid redistribution of IT resources to respond to rapid changes in business needs. However, enterprise users are more stringent than individual users in terms of stability requirements, such as factory operation control (MES) systems operating in factories or related manufacturing management systems, which may cause abnormalities due to cloud service servers or external networks. The disruption of cloud services will cause huge losses in yield and capacity. Therefore, in the past, enterprises have always been questioning and resisting when they turn their key operating systems into cloud service models.

Therefore, how to improve the stability of cloud services to meet the standards of enterprise users is an urgent problem to be solved. One aspect of the disclosure is a cloud service continuous line system, including a cloud server and a monitoring server, the cloud server provides a cloud service to process a transaction request, and the monitoring server is connected to the cloud server. And receiving the transaction request sent by a client device. The monitoring server comprises the following modules: an application service core module, a transaction temporary storage database, a diagnostic module, and a shunt and control module. The diagnostic module detects at least one state of the cloud server and determines whether the state is normal. The shunting and control module is electrically connected to the application service core module, and when the state is normal, the transaction is transmitted. Requiring to the cloud server, and when the status is abnormal, transmitting the transaction request to the application service core module, so that the application service core module executes a local service corresponding to the cloud service to process the transaction demand and generate a transaction data, the application service core module and using the transaction temporary data The library records the transaction data. After the state is returned to normal by the abnormality, a data synchronization module in the monitoring server synchronizes the transaction data in the transaction temporary database to a database accessible by the cloud server, and when the synchronization is performed, The transaction diversion and control module stores the current transaction demand retransmitted by the client device in a transaction queue provided by a transaction queue management module, and after the synchronization is completed, the transaction queue management module transmits the current transaction. Demand to the transaction diversion and control module.

Another aspect of the present disclosure is a cloud service continuity method, which includes the following steps. First, receiving a transaction request sent by a client device, and then detecting a status about a cloud server, and determining whether the state is normal. When the state is normal, the transaction request is transmitted to the cloud server, and the cloud server provides a cloud service to process the transaction request. When the status is abnormal, a local service is provided to process the transaction demand, and a transaction data generated when the local service is provided is stored in a transaction temporary database. After the state returns to normal by the abnormality, the transaction data in the transaction temporary database is synchronized to a database accessible by the cloud server, and when the synchronization is performed, the current transaction requirement of the user device is retransmitted. In a transaction queue, and after the synchronization is completed, if the state is normal, the current transaction demand is transmitted to the cloud uniform, otherwise the local service is used to process the current transaction demand.

The technical solution of the present disclosure can enable the client device to continuously transmit the transaction demand, obtain the uninterrupted cloud service, and solve the single point that the cloud service has always had when the network connection problem occurs or the cloud server is malfunctioning. Single point of failure The negative impact of road disconnection and instability on cloud service stability enables enterprise users to use cloud services in their critical systems, enjoy the benefits of cloud services and increase productivity.

100‧‧‧Cloud Service Continuous Line System

102‧‧‧Monitoring server

122‧‧‧Application Service Core Module

124‧‧‧Diagnostic Module

126‧‧‧Split and control module

128‧‧‧Transaction temporary database

130‧‧‧Data Synchronization Module

132‧‧‧Transaction queue management module

104‧‧‧Cloud Server

142‧‧‧Database

106‧‧‧Customer device

108‧‧‧Internal network

110‧‧‧External network

200‧‧‧Cloud service continuous line method

S202~S220‧‧‧Steps

The above and other objects, features, advantages and embodiments of the present invention will become more apparent and understood. The description of the drawings is as follows: FIG. 1 is a block diagram of a cloud service continuous line system according to the first embodiment. FIG. 2 is a flow chart of a cloud service continuity method according to the second embodiment.

The technical content is clearly disclosed in the following figures and detailed description, and is not intended to limit the present invention. Further, those skilled in the art can understand the listed embodiments, and the techniques that can be taught by the present invention, Changes and modifications may be made without departing from the spirit and scope of the invention.

Please refer to FIG. 1 . FIG. 1 is a block diagram showing a cloud service continuous line system according to the first embodiment. The cloud service continuity system 100 includes a monitoring server 102, a cloud server 104 and a client device 106. The monitoring server 102 can also be a computer system, and the client device 106 can be a personal computer, a mobile phone or a tablet or any device with networking capabilities. The monitoring server 102 is connected to the internal network 108 for use. The client device 106, the internal network 108 can be a wide area network, a regional network or a Bluetooth network, and the client device 106 transmits the transaction demand to the monitoring server 102 via the internal network 108. The monitoring server 102 is connected to the cloud server 104 via an external network 110. The external network 110 can be a wide area network or a regional network.

The cloud server 104 provides at least one cloud service that can handle the transaction requirements transmitted by the client device 106. The cloud server 104 can access a database 142 and store the transaction data generated when processing the transaction request to the repository 142. The cloud service provided by the cloud server 104 can be produced or operated by a company such as a Manufacturing Execution System (MES) service, an Enterprise Resource Planning (ERP) system service, or a Supply Chain Management system service. The services required can also be personal services such as cloud file image processing.

In the traditional cloud service mode, the client device 106 is directly connected to the cloud server 104. However, if the connection is abnormal, or the cloud server 104 fails, the transaction demand transmitted by the client device 106 cannot be processed. . Therefore, the disclosure provides a monitoring server 102 including an application service core module 122, a diagnostic module 124, a distribution and control module 126, and a transaction temporary database 128.

The function of the diagnostic module 124 is to view the status of the cloud server 104, and check the connection with the client device 106, and determine whether the operation of the system is normal according to the following, as follows. The diagnostic module 124 detects the monitoring server 102 and the internal network including the client device 106. If the internal network 108 is a local area network, the diagnostic module 124 can check whether the connection status of the internal network 108 is normal if the packet test is normal. If the packet test fails, the user terminal is indicated. The connection between the device 106 and the monitoring server 102 has been disconnected, and the transaction request cannot be transmitted. At this time, the diagnostic module 124 performs an alert action to remind the system maintenance personnel to repair the internal network 108 at the first time. In one embodiment, the diagnostic module 124 displays an alert message on the display device of the monitoring server 102. In another embodiment, the diagnostic module 124 issues a warning sound to the sound effect device of the monitoring server 102. In yet another embodiment The diagnostic module 124 sends a warning letter to notify the system maintenance personnel.

The diagnostic module 124 also detects at least one state regarding the cloud server 104 and determines whether the state is normal. In an embodiment, the state includes the connection state of the external network 110, and the diagnostic module 124 checks the connection state to the cloud server 104 using a packet test (PING), and determines the external network 110 when the packet test fails. The connection status is abnormal. In another embodiment, the diagnostic module 124 detects and records the connection rate with the external network 110. If the connection rate continues to decrease, or the connection rate continuously falls below a certain threshold for more than a period of time, the external determination is made. The connection status of the network 110 is abnormal.

The status of the cloud server 104 also includes the operating status of the cloud server 104. The status of the cloud server 104 is determined to be normal or abnormal by periodically sending the test transaction request to the cloud server 104 and analyzing the transaction reply time. In an embodiment, the diagnostic module 124 sets a transaction demand template for each type of transaction demand transmitted by the client device 106, and periodically sends different types of transaction demand templates to ensure different types of transaction needs. The cloud service provided by the cloud server 104 can be obtained, and when the out of service (OOS) occurs, the status is determined to be abnormal. In another embodiment, the diagnostic module 124 determines whether the cloud service provided by the cloud server 104 reaches a service level agreement (SLA) according to the transaction reply time of the test transaction request, and when the service level agreement is not reached. , to determine that the state is abnormal.

The diagnostic module 124 also monitors the transaction response time of the test transaction demand in different time segments through the statistical process control (SPC) analysis model, and transmits the analysis result back to the cloud server 104 to improve the operational stability. With reliability.

The diagnostic module 124 also determines the operation status of the cloud server 104 by periodically obtaining the internal operation status information of the cloud server 104 from the cloud server 104. The internal operation status information includes the health detection performed by the cloud server 104 on itself, such as the processor usage rate (CPU). Usage), disk space, network performance, memory usage, etc., may include detection of an internal installer or framework by the cloud server 104, the cloud server 104 also connects to other authentication servers to obtain authentication information, and the authentication cloud server 104 obtains services provided by other servers conforming to the service level agreement (SLA), and the cloud server 104 periodically generates the above-mentioned health status and certification information reports. In an embodiment, the diagnostic module 124 periodically obtains the health status and the authentication information report, and determines whether the operating status of the cloud server 104 is normal according to the content thereof. In another embodiment, the cloud server 104 adds an indicator to the health status and the authentication information report to indicate the overall status of the current cloud server 104. If the cloud service is normally provided, the diagnostic module 124 periodically obtains the health status and the authentication information report, and determines that the status is abnormal when the cloud server 104 cannot provide the cloud service normally, otherwise the status is determined. It is normal.

By testing the connection status of the internal network 108 and detecting the state of the cloud server 104, the diagnostic module 124 can discover that the service of the cloud server 104 cannot be obtained at the first time, and utilizes the shunt and control modes. The group 126 and application service core module 122 enable the transaction requirements transmitted by the client device 106 to be processed continuously. When the diagnostic module 124 determines that the status is normal, the offloading and control module 126 transmits the transaction request transmitted by the client device 106 to the cloud server 104, and the cloud service provided by the cloud server processes the transaction request. When the diagnostic module 124 determines that the status is abnormal, the transaction request is transmitted to the application service core module 122, and the application service core module 122 provides a local service corresponding to the cloud service to replace the cloud server 104 to process the transaction. demand.

In order to continuously process the transaction requirements transmitted by the client device 106, the local service provided by the application service core module 122 needs to be able to process all kinds of transaction requirements transmitted by the client device 106. The virtual machine (Virtual Machine) is installed on the application service core module 122, and the executable component of the cloud service provided by the cloud server 104 is installed to be abnormal when the network connection state is abnormal or the operation state of the cloud server 104 is abnormal. A local service is provided to process the transaction demand transmitted by the client device 106, and the transaction data generated by processing the transaction request is stored in the transaction temporary database 128. In an embodiment, the cloud service provided by the cloud server 104 Including Manufacturing Execution System (MES) services, Enterprise resource planning (ERP) system services, and Supply chain management system services, the client device 106 leases Manufacturing Execution System (MES) services. Therefore, the application service core module 122 in the monitoring server 102 connected to the internal network 108 of the client device 106 will only install an execution component that provides a manufacturing execution system (MES) service on its virtual machine. In another embodiment, the client device 106 leases an enterprise resource planning (ERP) system service, so the application service core module 122 in the monitoring server 102 connected to the client device 106 via the internal network 108 will only be in the An execution component that provides enterprise resource planning (ERP) system services is installed on its virtual machine.

In order for the cloud server 104 to access the complete transaction data, when the diagnostic module 124 determines that the status is restored to normal by the abnormality, the data synchronization module 130 synchronizes the transaction data in the transaction temporary database 128 to the database 142. The transaction queue management module 132 provides a transaction queue. When the data synchronization module 130 synchronizes, the transaction distribution and control module 126 stores the current transaction requirements retransmitted by the client device 106 into the transaction queue. After the synchronization is completed, the transaction queue management module 132 transmits the current transaction demand in the transaction queue to the transaction distribution and control module 126, and the transaction distribution and control module 126 determines the current transaction demand according to the status of the output of the diagnostic module 124. The transfer to the cloud server 104 or the application service core module 122 is processed. In this way, when the system is operating normally, the processing of the transaction requirements is smoothly transferred back to the cloud server 104.

In one embodiment, the transaction queue management module 132 is first in, first out. (FIFO) mode sends the current transaction demand in the transaction queue. In another embodiment, the transaction queue management module 132 prioritizes the types of current transaction requirements and transmits the current transaction requirements in accordance with the priority order. In yet another embodiment, the transaction diversion and control module 126 periodically checks the number of current transaction requirements in the transaction queue when synchronizing, and when the application reaches an upper limit (eg, 10 strokes), the application service core module 122 Processes the 10 current transaction requests that were transmitted the earliest to avoid the transaction response time of the current transaction demand is too long.

The application service core module 122, the diagnostic module 124, the shunt and control module 126, the data synchronization module 130, and the transaction queue management module 132, as described above, may be software, hardware, and/or Or carcass. For example, if the execution speed and accuracy are the primary considerations, the modules can basically be dominated by hardware and/or carcass; if design flexibility is the primary consideration, then the modules are basically The software is mainly used; or, the modules can work together with software, hardware and carcass. It should be understood that the above examples are not intended to limit the present invention, and are not intended to limit the present invention. Those skilled in the art will be able to flexibly select the specific embodiments of the modules as needed. For example, the modules can be integrated into a central processor for execution.

The transaction temporary storage database 128 and the data library 142 as described above may be separately stored in different storage devices or stored in the same storage device, such as a computer hard disk or other computer readable recording medium. Wait. Those skilled in the art can understand that the above-mentioned data content stored in each database is named only to make the technology of the present case more obvious and understandable, and is not limited to the number of databases and stored. Data content. It is still an embodiment of the present invention to integrate the transaction temporary database 128 and the database 142 into one database or into a plurality of databases, or to replace the contents of the data into another database for storage.

Referring to FIG. 2, FIG. 2 is a flow chart of a cloud service continuous line method according to the second embodiment. For convenience and clarity of description, the following description of the cloud service continuity method is exemplified by the cloud service continuity system 100 shown in FIG. 1, but the disclosure is not limited thereto.

The cloud service continuity method 200 includes the following steps. Step S202 is to receive a transaction request sent by a client device 106. In an embodiment, the detecting in step S202 includes detecting a connection state of the internal network 108 of the client device 106 by using a packet test (PING), when the connection state of the internal network 108 is abnormal. , perform a warning action. In one embodiment, the alert action is to display an alert message on a display device. In another embodiment, the alert action is to sound a warning sound using a sound effect device, and in yet another embodiment, to send a warning letter notification system. Maintenance personnel. Since the connection status of the internal network 108 is abnormal, indicating that the transaction demand cannot be transmitted, step S202 is performed to enable the system maintenance personnel to repair the internal network 108 at the first time.

After confirming that the sending operation of the transaction request is normal, step S204 is to detect at least one state about a cloud server 104, and determine whether the state is normal. In an embodiment, the state is a connection state of the external network 110 connected to the cloud server 104, and the step S204 detects the connection state of the external network 110 by a packet test (PING), and if the packet test fails, it is determined. The connection status of the external network 110 is abnormal, and the external network is also detected. If the connection rate continues to decrease, or the connection rate continuously falls below a certain threshold for more than a period of time, it is determined that the connection state of the external network 110 is abnormal.

In another embodiment, the state is an operating state of the cloud server 104. In step S204, the test transaction request is periodically sent to obtain a transaction reply time of the test transaction demand, and the transaction reply time is analyzed to determine that the state is normal. Or abnormal. The operation of analyzing the transaction reply time includes whether the transaction reply time violates the service level agreement (SLA), whether the transaction reply time is longer than the preset standard, whether the service stop (OOS) occurs, and when any of the above conditions is yes, the cloud servo is determined. The operational state of the device 104 is abnormal.

In another embodiment, the state is an operating state of the cloud server 104. In step S204, the at least one internal operating state information is obtained from the cloud server 104, and the operating state is determined according to the internal operating state information. Normal or abnormal. The internal operational status information includes the health detection performed by the cloud server 104 on itself, including CPU usage, disk space, network performance, and memory usage. In addition, the cloud server 104 can also detect the internal installation program or framework. The cloud server 104 also connects to other authentication servers to obtain authentication information, and authenticates the services provided by other servers to the cloud server 104. The service level agreement (SLA) is met, and the operation status of the cloud server 104 is determined to be normal or abnormal according to the above internal operation status information.

The purpose of step S204 is to confirm that the cloud server 104 can provide the cloud service processing transaction request, and if the step S204 determines that the status is normal, In step S220, the transaction request is transmitted to the cloud server 104, and the cloud server 104 provides at least one cloud service to process the transaction request. The cloud server 104 and the cloud service details it provides are as described above.

However, if it is determined in step S204 that the status is abnormal, it indicates that the cloud service provided by the cloud server 104 cannot be used. In this case, step S210 is performed to provide at least one local service to process the transaction demand, and the transaction data generated when the local service is provided. Save to transaction temporary database 128. The details of providing local services are as described above.

After the state returns to normal, it needs to be converted back to the cloud service provided by the cloud server 104. In this case, step S212 is performed to synchronize the transaction data in the transaction temporary storage database 128 to the cloud server 104 to access a database. 142, so that the cloud server 104 can access the complete transaction data. When the synchronization is performed, since the cloud server 104 has not yet obtained the complete transaction data, the current transaction demand retransmitted by the client device 106 is stored in a transaction queue.

After the synchronization is completed, step S214 is performed to process the current transaction demand in the transaction queue, and step S210 or step S220 is determined according to whether the state is normal or not. In one embodiment, the current transaction demand in the transaction queue is processed in a first in first out (FIFO) manner. In another embodiment, prioritization is given according to the type of current transaction demand and the current transaction demand is processed in order of priority. After the processing of the current transaction demand in the transaction queue is completed, the processing of the transaction requirement is completely converted back to the cloud server 104, so that the client device 106 can be disconnected from the cloud server 104 or the cloud server 104. The state of operation affects and enjoys cloud services without interruption.

Although the present invention has been disclosed in the above embodiments, it is not intended to limit the present invention, and the present invention can be modified and modified without departing from the spirit and scope of the present invention. The scope is subject to the definition of the scope of the patent application attached.

100‧‧‧Cloud Service Continuous Line System

102‧‧‧Monitoring server

122‧‧‧Application Service Core Module

124‧‧‧Diagnostic Module

126‧‧‧Split and control module

128‧‧‧Transaction temporary database

130‧‧‧Data Synchronization Module

132‧‧‧Transaction queue management module

104‧‧‧Cloud Server

142‧‧‧Database

106‧‧‧Customer device

108‧‧‧Internal network

110‧‧‧External network

Claims (15)

A cloud service continuous line system, comprising: a cloud server, providing at least one cloud service to process at least one transaction requirement; and a monitoring server connected to the cloud server for receiving the transaction sent by a client device The monitoring server includes: an application service core module; a transaction temporary storage database electrically connected to the application service core module; and a diagnostic module detecting at least one state of the cloud server, And determining whether the state is normal; and a shunting and control module electrically connected to the application service core module, when the state is normal, the shunting and control module transmits the transaction demand to the cloud server, when When the status is abnormal, the shunting and control module transmits the transaction request to the application service core module, so that the application service core module executes at least one local service corresponding to the cloud service to process the transaction demand and generate a Transaction data, the transaction temporary database records the transaction data. The cloud service continuity system of claim 1, wherein the client device is connected to the monitoring server through an internal network, and the diagnostic module tests that the connection status of the internal network is normal or abnormal. The diagnostic module performs a warning action when the connection state of the internal network is abnormal. The cloud service continuity line system according to claim 1, wherein the monitoring server is connected to the cloud server through an external network, wherein the state includes a connection state of the external network, and the diagnostic module tests The connection status of the external network is normal or abnormal. The cloud service continuous line system according to claim 1, wherein the state includes an operating state of the cloud server, the diagnostic module periodically sends out a test transaction demand and obtains a transaction reply time, and analyzes the transaction reply time to determine The operating state of the cloud server is normal or abnormal. The cloud service continuous line system of claim 1, wherein the state includes an operating state of the cloud server, and the diagnostic module obtains at least one internal operating state information from the cloud server to determine the cloud server. The operational status is normal or abnormal. The cloud service continuous line system according to any one of claims 1 to 5, further comprising: a data synchronization module, after the abnormality returns to normal in the state, synchronizing the transaction data in the transaction temporary database to the The cloud server can access a database; and a transaction queue management module provides a transaction queue. When the data synchronization module synchronizes, the transaction distribution and control module retransmits the client device. At least one current transaction demand is stored in the transaction queue, and after the synchronization is completed, the transaction queue management module transmits the current current in the transaction queue Transaction demand to the transaction diversion and control module. The cloud service continuity system according to claim 6, wherein the transaction queue management module transmits the current transaction demand in the transaction queue to the transaction distribution and control module in a first-in first-out mode. The cloud service continuity system according to claim 1, wherein the application service core module utilizes a virtual machine environment to execute the local service. A cloud service continuity method includes: (a) receiving at least one transaction request sent by a client device; (b) detecting at least one state about a cloud server, and determining whether the state is normal; (c) When the state is normal, the transaction request is transmitted to the cloud server, the cloud server provides at least one cloud service to process the transaction request; and (d) when the state is abnormal, at least one local service is provided to process the Transaction demand, and a transaction data generated when the local service is provided is stored in a transaction temporary database. The cloud service continuity method according to claim 9, further comprising: detecting a connection state including an internal network of the client device, and when the connection state of the internal network is abnormal, executing one Warning action. The cloud service continuity method according to claim 9, wherein the state further comprises a connection state of an external network connected to the cloud server, and the step (b) further comprises testing the connection of the external network. Status to determine if the status is normal. The cloud service continuity method according to claim 9, wherein the state further comprises an operating state of the cloud server, and the step (b) further comprises: periodically sending a test transaction request to obtain a transaction reply time, and analyzing the transaction. The reply time is used to judge whether the operating state of the cloud server is normal or abnormal. The cloud service continuity method according to claim 9, wherein the state further comprises an operating state of the cloud server, and the step (b) further comprises: obtaining at least one internal operating state information from the cloud server, and according to The internal operation status information determines that the operating state of the cloud server is normal or abnormal. The cloud service continuous line method as claimed in any one of claims 9 to 13, further comprising the steps of: synchronizing the transaction data in the temporary storage database to the cloud server after the state is returned to the normal state by the abnormality; Accessing a database; during synchronization, storing at least one current transaction demand retransmitted by the client device in a transaction queue; After the synchronization is completed, it is decided whether the current transaction demand in the transaction queue is transmitted in step (c) or (d) according to whether the state is normal or not. The cloud service continuity method according to claim 14, wherein after the synchronization is completed, the transaction demand in the transaction queue is transmitted in a first-in first-out mode.