JP2019135578A - Cloud system, cloud server, edge server and user device - Google Patents

Abstract

To solve the problem in which a service provided by collaboration between a cloud and an edge is vulnerable to environmental changes in a service operation.SOLUTION: A cloud system according to the embodiment comprises a cloud server, an edge server and a user device capable of communicating with each other via a network. The cloud server, the edge server and the user device comprise their middlewares operating on their own machines and functioning at a lower layer of a service. This middleware comprises a monitoring function, a switching function and a redistribution function. The monitoring function monitors the network state and each operating state of the cloud server, the edge server and the user device. The switching function switches a system configuration including a network topology based on the monitoring result. The redistribution function redistributes an operating location of the service according to switching the system configuration.SELECTED DRAWING: Figure 3

Description

  Embodiments described herein relate generally to a technology for providing a service by linking a cloud server and an edge server.

  Cloud computing is drawing attention. Cloud computing is a general term for technologies that provide services such as storage and applications using a server group (cloud). A service user (such as a terminal device) receives a service via a communication network represented by the Internet. Broadly classified systems such as SaaS (Software as a Service), PaaS (Platform as a Service), and IaaS (Infrastructure as a Service) are known. SaaS is a system that provides an application (software) as a service. PaaS is a system that provides a platform (platform) for running an application as a service. IaaS is a system in a form that provides resources such as a server device, a central processing unit, and storage as a service (public cloud).

  As IoT (Internet of Things) technology spreads, edge computing has attracted attention. Edge computing is a collective term for systems that cooperate with cloud computing after distributing and distributing small-scale servers (edges) compared to the cloud and distributing data generated in the vicinity for each edge. A user can access a nearby edge server via a network such as a subscriber network, and can use the service with a faster response than the cloud.

Japanese Patent Laid-Open No. 2006-82465 Japanese Patent Laying-Open No. 2015-56831 JP 2014-3535 A JP 2006-323767 A JP 2006-50086 A Special table 2015-505404 gazette

  Both cloud computing and edge computing are operated on the premise of a robust information communication infrastructure. For this reason, it is difficult to sufficiently provide a service requested by a user in a narrow communication band or an unstable communication environment. For example, even if one server in the system fails, the user may not receive the expected service. Furthermore, the service provided by this type of system is fixed regardless of the installation location or network environment. This was also a factor that brought vulnerability to environmental changes.

  Therefore, an object is to provide a cloud system, a cloud server, an edge server, and a user device that are robust against environmental changes in operation.

  The cloud system according to the embodiment includes a cloud server, an edge server, and a user device that can communicate with each other via a network. In this cloud system, a cloud server, an edge server, and a user device each include middleware that functions in a lower layer of a service that operates on its own machine. This middleware has a monitoring function, a switching function, and a redistribution function. The monitoring function monitors the status of the network and the operating status of each of the cloud server, the edge server, and the user device. The switching function dynamically switches the system configuration including the network topology based on the monitoring result. The redistribution function redistributes the service destinations according to the switching of the system configuration.

FIG. 1 is a diagram illustrating an example of a cloud system according to the embodiment. FIG. 2 is a diagram showing an example of a service form in the system shown in FIG. FIG. 3 is a block diagram illustrating an example of functions provided in the middleware MW. FIG. 4 is a diagram illustrating an example of a system configuration according to the embodiment. FIG. 5 is a diagram illustrating another example of the system configuration according to the embodiment. FIG. 6 is a diagram illustrating another example of the system configuration according to the embodiment. FIG. 7 is a diagram illustrating another example of the system configuration according to the embodiment. FIG. 8 is a diagram illustrating an example of a transition of the service form with the movement of the user device 10. FIG. 9 is a flowchart illustrating an example of a processing procedure of the middleware MW according to the embodiment. FIG. 10 is a diagram illustrating an example of priority management of operating devices for each service. FIG. 11 is a flowchart illustrating an example of a processing procedure related to redistribution of the operation destinations of each service. FIG. 12 is a diagram illustrating an example of a hardware configuration of the edges 201 and 202.

  FIG. 1 is a diagram illustrating an example of a cloud system according to the embodiment. In FIG. 1, a user device 10 possessed by a user is connected to one of edges 201 and 202 via a communication network 20. This communication line may be either a public infrastructure network or a network uniquely constructed by a user, or may be a wireless line or a wired line.

  The edges 201 and 202 are, for example, portable server computers, and are connected to the cloud 100 via the communication network 30 which is a public network or a unique network. The entity of the cloud 100 can be understood as, for example, a cloud server or a server group in which a plurality of servers are connected.

  FIG. 2 is a diagram showing an example of a service form in the system shown in FIG. In the embodiment, the middleware MW is incorporated in the user device 10 in advance. All of the various services (applications) a that can be used from the user apparatus 10 operate on the middleware MW.

  Similarly, the middleware MW is incorporated in the edges 201 and 202 and the cloud 100 in advance. The service b that realizes the functions of the edges 201 and 202 operates on the middleware MW. In addition, the service c that realizes the function of the cloud 100 also operates on the middleware MW. That is, the cloud 100, the edges 201 and 202, and the user device 10 each include middleware MW that functions in a lower layer of a service that operates on its own device.

  The middleware MW links the user apparatus 10, the edges 201 and 202, and the cloud 100 with each other, and dynamically switches the system form based on the network environment status and the device operation status.

  FIG. 3 is a block diagram illustrating an example of functions provided in the middleware MW. The middleware MW includes a monitoring function f1, a switching function f2, a redistribution function f3, and a management function f4. The monitoring function f1, the switching function f2, the redistribution function f3, and the management function f4 are a CPU (Central Processing Unit) as hardware in the cloud 100, the edges 201 and 202, and the user device 10 as computers or computer systems. ) And a memory and a program as software operate in cooperation with each other.

  That is, the monitoring function f1, the switching function f2, the redistribution function f3, and the management function f4 can be implemented in each device (cloud 100, edges 201 and 202, and user apparatus 10) as programs. The monitoring function f1, the switching function f2, the redistribution function f3, and the management function f4 may operate independently in the mounted device, or are mounted in the cloud 100, the edges 201 and 202, and the user device 10. The middleware MW may perform a cooperative operation by communicating with each other.

The monitoring function f1 monitors the status of the communication networks 20 and 30 and the operation statuses of the cloud 100, the edges 201 and 202, and the user device 10.
The switching function f2 dynamically switches the system configuration such as the topology of the communication networks 20 and 30 based on the result of monitoring by the monitoring function f1.

  The redistribution function f3 redistributes the service destinations in accordance with the switching of the system configuration by the switching function f2. That is, the redistribution function f3 updates the devices (cloud 100, edges 201 and 202, and user apparatus 10) that are the operation destinations of the services a, b, and c as the system configuration is switched.

  The management function f4 manages, for each of the services a, b, and c, a device at the operation destination with a priority from the cloud 100, the edges 201 and 202, and the user device 10. The redistribution function f3 redistributes the operation destinations of the services a, b, and c according to the priority managed by the management function f4.

  FIG. 4 is a diagram illustrating an example of a system configuration according to the embodiment. FIG. 4 shows an example of a system configuration that can be applied when an access failure to the cloud 100 occurs in the system shown in FIG. For example, when the cloud 100 goes down, or when the communication goes out of range of the communication network 30 or a communication failure occurs even within the range, the middleware MW connects the edge 201 and the user devices 10 under its control. The system is reconstructed in a form connected by the communication network 20. This service form is referred to as <edge single form>.

  FIG. 5 is a diagram showing another example of the system configuration when a failure occurs in the system shown in FIG. A service form similar to that in FIG. 4 can be established between the edge 202 and the user devices 10 under the edge 202. Then, the middleware MW reconstructs the system in a form in which the edges 201 and 202 are connected via the public network or the communication network 40 which is a unique network. This service form is referred to as <inter-edge connection form>.

  As shown in FIG. 6, for example, when the edge 201 is down, the middleware MW reconstructs the system so as to continue the service with the user device 10 under the edge 201 alone. This service form is referred to as <device unit form>.

  As shown in FIG. 7, if the communication network 20 is healthy, the middleware MW reconstructs the system in a form in which the user devices 10 under the edge 201 are connected by the communication network 20. This service form is referred to as <inter-device connection form>.

  FIG. 8 is a diagram illustrating an example of a transition of the service form with the movement of the user device 10. If the cloud 100, the edge 201, and the communication networks 30 and 20 are all healthy, the service is provided in a service form called <basic form>. In the <basic form>, the service a operates on the middleware MW of the user apparatus 10, the service b operates on the middleware MW of the edge 201, and the service c operates on the middleware MW of the cloud 100.

  It is assumed that the edge 201 moves out of the communication network 30 from this state, and communication between the edge 201 and the cloud 100 becomes impossible. Then, the middleware MW switches the system configuration to <edge single form> and redistributes the operation destination of the service c from the cloud 100 to the edge 201. As a result, the service “a” of the user apparatus 10 can be continuously provided using the resources of the edge 201.

  Furthermore, when communication between the edge 201 and the cloud 100 is restored from this state, the middleware MW switches the system configuration to <basic form> and redistributes the operation destination of the service c from the edge 201 to the cloud 100. As a result, the service a of the user apparatus 10 can be provided again in a form that uses the resources of the cloud 100 and the edge 201.

  FIG. 9 is a flowchart illustrating an example of a processing procedure of the middleware MW according to the embodiment. The middleware MW constantly monitors the connection status of the communication networks 20 and 30 (step S1). For example, at the edge 201, it is determined whether or not the connection with the host network (communication network 30) is healthy (step S2). If No in step S2, the middleware MW determines whether or not the connection with the adjacent network (communication network 20) is healthy (step S6). If No in step S6, the middleware MW switches the system configuration to the single operation configuration (step S10). As a result, the provision of the service in the <edge single form> or the <device single form> is started.

  If the connection with the upper network is healthy in step S2 (Yes), the middleware MW monitors the operation status of the device (step S3) and determines whether the upper device (device) is operating normally. (Step S4). If No in step S4, the processing procedure proceeds to step S6. If Yes in step S4, the middleware MW switches the system configuration to a configuration for connecting to the upper device (step S5). As a result, provision of services in the <basic form> or the <edge connection form> is started.

  On the other hand, if Yes in step S6, the middleware MW monitors the operation status of the device (step S7), and determines whether the adjacent device is operating normally (step S8). If No in step S8, the processing procedure proceeds to step S10. If Yes in step S8, the middleware MW switches the system configuration to a configuration for connecting to an adjacent device (step S9). As a result, the provision of services in the <inter-edge connection form> or <inter-device connection form> is started.

  FIG. 10 is a diagram illustrating an example of priority management of operating devices for each service. As illustrated in FIG. 10, the operation destination of the service a is set in the order of high priority in the order of cloud, edge, and user device. The operation destination of the service b is set with a higher priority in the order of edge and user device. The operation destination of the service c is set in the user device. Such priority information is stored in advance in a memory of a computer (cloud 100, edges 201 and 202, user device 10) on which middleware MW is mounted.

  In the <basic form>, a state is realized in which the service a operates in the cloud, the service b operates in the edge, and the service c operates in the user apparatus. This is a state in which each service a, b, and c is operating at an operating destination with priority 1 (highest).

  When switching from this state to <edge single form>, the operation destination of the service a is redistributed to the edge having the priority 2. As a result, the service a and the service b are operated at the same edge (for example, the edge 201).

  Further, when switching to <device single form>, the operating destination of service a is redistributed to user devices with priority 3, and the operating destination of service b is also redistributed to user devices (priority 2). As a result, the service a, the service b, and the service c are in a state of operating on the same user device 10.

  FIG. 11 is a flowchart illustrating an example of a processing procedure related to redistribution of the operation destinations of each service. In FIG. 11, when the system configuration changes (step S21), the middleware has the highest priority for operating each service among the devices (cloud 100, edge 201, 202, user device 10) that can be operated at that time. The device is specified according to the priority information as shown in FIG. 10 (step S23). The processes described below are sequentially performed for each service (step S22).

  If the device that operates the service is the own device, that is, if the operation destination with the highest priority is the own device (Yes in step S24), the middleware MW determines whether or not the service is operating on the own device. If it is determined to be No (step S25) and No, the service is immediately operated by the own machine (step S26).

  On the other hand, if the answer is No in step S24, the middleware MW determines whether or not the service is operating on its own device (step S28). If the service is Yes, the middleware MW immediately stops the service that is operating on the own device. (Step S29). If Yes in step S25 or No in step S28, the processing procedure moves to step S27, and steps S23, S24, S25, S26, S28, and until all the services are processed. The process of step S29 is repeated.

  FIG. 12 is a diagram illustrating an example of a hardware configuration of the edges 201 and 202. In this embodiment, the middleware MW and services of the edges 201 and 202 can be applied to various hardware, so to speak, as an outdoor environment type edge, the built-in battery 80, the wired / wireless router 70, the hub ( HUB) 60 and board 50 are mounted. The board 50 includes various connectors 11, a storage 12, a chip set 13, and the like. By installing the middleware MW in the chipset 13 and the storage 12 and integrating the edges 201 and 202, merits such as cost reduction, transportation amount reduction, and size reduction can be obtained. In addition, with the above configuration, it is possible to provide an edge device suitable for the outdoor environment by integrating power, communication, and service.

  As described above, in this embodiment, the dedicated middleware MW is incorporated in the user device 10, the edges 201 and 202, and the cloud 100, and the service used by the user device 10 is operated on the middleware MW. The middleware MW constantly monitors the operation statuses of the communication networks 20 and 30, the user device 10, the edges 201 and 202, and the cloud 100.

  The middleware MW is a system when the network connection status changes (for example, when the network moves to a place where the network is not connected outside) or when the operation status of the device changes (for example, when a cloud or edge device goes down). Switch configuration automatically.

  Further, the middleware MW manages the priority of the device (user device 10, edge 201, 202, cloud 100) as an operation destination for each service. Based on the priority, the middleware dynamically redistributes the devices to be operated for each service according to the operation status of the communication network and the devices. The middleware MW operates a service assigned to each device, requests the operating device in response to a service use request from the user, and provides a processing result to the user.

  By using the user device 10 in which the middleware MW is incorporated, the user can use all services without being conscious of the network and device configuration.

  In this way, by dynamically switching the system configuration and service operating devices, all services can be used continuously even in a narrow band or unstable network environment. In other words, by dynamically switching the system configuration and service operating devices, all services can be used continuously regardless of location or environment. Even when the network is not connected (failure, disconnection, out of service area, etc.), or when the cloud 100 and the edges 201 and 202 are down, the service can be used continuously. Furthermore, by making the middleware MW and services of the edges 201 and 202 applicable to various hardware, a device suitable for the outdoor environment can be realized.

  Therefore, it is possible to provide a cloud system, a cloud server, an edge server, and a user device that are robust against changes in the operational environment.

  Although an embodiment has been described, this embodiment is presented as an example and is not intended to limit the scope of the invention. The novel embodiment can be implemented in various other forms, and various omissions, replacements, and changes can be made without departing from the scope of the invention. This embodiment and its modifications are included in the scope and gist of the invention, and are included in the invention described in the claims and the equivalents thereof.

  DESCRIPTION OF SYMBOLS 10 ... User apparatus, 11 ... Connector, 12 ... Storage, 13 ... Chipset, 20, 30, 40 ... Communication network, 50 ... Board, 60 ... Hub (HUB), 70 ... Wired / wireless router, 80 ... Built-in battery, DESCRIPTION OF SYMBOLS 100 ... Cloud, 201, 202 ... Edge, f1 ... Monitoring function, f2 ... Switching function, f3 ... Redistribution function, f4 ... Management function.

Claims (5)

A cloud system including a cloud server, an edge server, and a user device that can communicate with each other via a network,
The cloud server, the edge server, and the user device each include middleware that functions in a lower layer of a service that operates on its own machine,
The middleware is
A monitoring function for monitoring the status of the network and the operating status of each of the cloud server, the edge server, and the user device;
A switching function that dynamically switches the system configuration including the topology of the network based on the monitoring result;
A cloud system comprising a redistribution function that redistributes the operation destination of the service in accordance with the switching of the system configuration. The middleware further includes a management function for managing the operation destination for each service with priority from the cloud server, the edge server, and the user device,
The cloud system according to claim 1, wherein the redistribution function redistributes an operation destination of the service according to the priority.   The cloud server used in the cloud system according to claim 1, comprising a service that functions on the middleware.   The edge server used in the cloud system according to claim 1, wherein the edge server includes a service that functions on the middleware.   The user apparatus used in the cloud system according to claim 1, comprising a service that functions on the middleware.