Edge computing devices
The edge computer device automates cluster construction and application deployment in a local network, addressing the need for specialized knowledge and ensuring stable, secure access to applications, even during hardware failures.
Patent Information
- Application Number
- JP2024025811
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-02-22
- Publication Date
- 2026-11-19
- Estimated Expiration
- 2044-02-22
AI Technical Summary
Existing systems require specialized knowledge for configuring and deploying applications in a container orchestration tool, making it difficult for users to manage clusters, verify application trustworthiness, ensure secure access, and maintain stable operation independent of internet connectivity.
An edge computer device with a container orchestration tool that automates cluster construction, application deployment, and secure access, utilizing a unit management application, service advertisement application, and application management application to manage applications in a local network without requiring specialized knowledge.
Enables easy installation and high availability of applications, ensuring functionality during hardware failures or maintenance, and secure access without relying on internet connectivity.
Smart Images

Figure 0007953812000001 
Figure 0007953812000002 
Figure 0007953812000003
Abstract
Description
TECHNICAL FIELD
[0001] The present invention relates to an edge computer device that operates an application in a container environment managed by a container orchestration tool in a local network, and particularly relates to an edge computer device that enables any application to be easily implemented and operated without requiring specialized knowledge or complicated operations.
BACKGROUND ART
[0002] Centered on cloud services and the like, virtualization technology that allows multiple applications to operate independently on the same machine has been advanced for the purpose of improving the utilization efficiency of physical servers, and Patent Document 1 proposes a container virtualization technology that downloads and executes an application in the container environment of a virtual machine.
[0003] Container orchestration tools are used to manage container environments running on multiple physical machines and improve system availability. A container orchestration tool is a tool that automatically attempts to maintain a predefined state of containers on a cluster composed of multiple physical machines.
[0004] Specifically, if one physical machine constituting the cluster becomes unable to operate due to a failure or the like, the application running on that machine becomes inoperable. At this time, the container orchestration tool can automatically perform alternative processing such as causing the application of the failed machine to run on another physical machine so as to achieve the predefined state.
PRIOR ART DOCUMENTS
PATENT DOCUMENTS
[0005]
PATENT DOCUMENT 1
SUMMARY OF THE INVENTION
[0006] A group of machines comprised of a container orchestration tool is called a cluster, and the machines that make up the cluster are called nodes. Generally, a node consists of at least one master node that provides the container execution environment and manages the cluster, and worker nodes that provide only the container execution environment. Initially, these nodes need to be connected to an IP network and configured to communicate with each other, and then the cluster needs to be configured by operating the container orchestration tool. However, these connections and configurations require specialized knowledge and are extremely difficult for users to perform on their own.
[0007] Furthermore, in order to actually utilize these functions, it is necessary to deploy (place) the container application to be used on the cluster, but deploying an application requires complex operations, making it difficult for end users to deploy various applications themselves.
[0008] Furthermore, even if a user is able to deploy an application themselves, verifying whether that application is trustworthy and not malicious is extremely difficult.
[0009] Furthermore, for users to utilize deployed applications, they need to be able to securely access the container applications running on the cluster from their own devices. However, existing systems are designed on the premise that end users access the cloud platform, and therefore cannot ensure easy access to the applications.
[0010] Furthermore, with the spread of cloud services, a wide variety of services are being provided on servers in the cloud. However, since using cloud services requires an internet connection, advanced security measures are necessary. Also, because service quality depends on the internet environment, there was a possibility that the service might become unavailable due to unforeseen circumstances, potentially hindering stable operation.
[0011] The objective of the present invention is to solve the above technical problems and provide an edge computer device that can provide a wide variety of applications with fewer hardware resources using container technology, through simple operation that does not require specialized knowledge, in a local network environment that does not depend on the internet environment. [Means for solving the problem]
[0012] To achieve the above objective, the present invention is characterized by having the following configuration in an edge computer device that runs applications in a container environment on a local network.
[0013] (1) The system comprises at least one container unit that functions as a node for realizing a container environment, a socket for the container unit that connects each container unit to the hardware resources of an edge computer device including other container units in a detachable manner, a container orchestration tool that manages the container units connected to the socket for the container unit as a cluster, a unit management application for managing the units, an application management application for managing the applications, and a service advertisement application that responds to name resolution requests from terminals.
[0014] (2) The edge computer device also includes the functions of an office automation (OA) device, and further comprises at least one OA unit for controlling the OA device, and sockets for OA units for connecting each OA unit to the hardware resources of the edge computer device.
[0015] (3) At least one of the container units is a master unit that operates as a master node in the container orchestration tool, and the rest are worker units that operate as worker nodes. A unit management application running on a cluster composed of these nodes is equipped with an API for operating the container orchestration tool, and new container units added or removed on the local network, as well as user terminals, can operate the master unit and worker units via the API.
[0016] (4) The worker unit, when connected to a socket for a container unit, is equipped with a unit initialization means that searches for a master unit and requests registration and connection to its own master unit.
[0017] (5) The unit management application running on the cluster is configured to respond to connection requests from worker units and add those worker units to the cluster.
[0018] (6) The application management application running on the cluster is configured to perform license authentication for applications that have been requested to be deployed, and to download authenticated applications and deploy them to the designated container.
[0019] (7) Service advertisement applications running on the cluster are configured to receive a multicast name resolution request from a user terminal on the local network, determine whether the corresponding FQDN is registered, and return a name resolution response if it is registered. [Effects of the Invention]
[0020] According to the present invention, for the reasons detailed below, end users can easily construct edge computing devices that offer high availability, allowing them to freely install applications, and that can continue to provide functionality even during accidental hardware failures or maintenance.
[0021] (1) A unit management application, which is an API server for managing units on a cluster, is implemented, so that worker units on a local network can register their own units to the cluster via the API. This makes it possible to automate cluster construction, and eliminates the need for settings and work that require specialized knowledge and operations.
[0022] (2) A service advertisement application that responds to name resolution requests by mDNS is implemented, which eliminates the need for settings and work that require specialized knowledge and operations, such as constructing a DNS server.
[0023] (3) A unit initialization unit is implemented in the master unit and the worker units to automate the registration of worker nodes to the master node, and a unit management application is implemented on the cluster to automate the addition and deletion of worker nodes to and from the cluster. This eliminates the need for settings and work that require specialized knowledge and operations, such as node construction.
[0024] (4) A plurality of units connected to sockets on a motherboard are clustered, and application deployment and the like are managed by a container orchestration tool, so that functions can continue to be provided even during accidental hardware failures or maintenance.
[0025] (5) End users can easily introduce and use applications via the API or a pre-installed configuration / deployment application, which greatly reduces the time required to resolve business issues. [Brief Description of the Drawings]
[0026] [Figure 1] This is a diagram schematically showing the configuration of a key telephone main unit (edge computer) according to an embodiment of the present invention. [Figure 2] This is a functional block diagram showing the configurations of a master unit and worker units that constitute a cluster managed by a container orchestration tool. [Figure 3]This is a flowchart illustrating the operation of the master unit initialization section. [Figure 4] This is a flowchart illustrating the operation of the worker unit initialization section. [Figure 5] This is a flowchart illustrating the operation of the unit management application. [Figure 6] This is a flowchart illustrating the operation of the app management application. [Figure 7] This is a flowchart illustrating the operation of a service advertising application. [Figure 8] This is a sequence diagram illustrating the operation of a service advertisement application. [Modes for carrying out the invention]
[0027] Embodiments of the present invention will be described in detail below with reference to the drawings. Figure 1 is a schematic diagram showing the configuration of an edge computing system to which the present invention is applied, in which an edge computer device 1 according to one embodiment of the present invention is interconnected with a number of end-user terminals 2, including an administrator terminal, via a local IP network.
[0028] In this embodiment, the edge computer device 1 is configured to accommodate multiple OA units 201 and container units 202. In addition to edge computer functionality that runs various applications in a container environment provided by the container units 202, the OA units 201 can also perform functions as general office automation equipment / devices. In this embodiment, we will particularly describe an example where the edge computer device 1 is a business phone main unit 10 that implements an OA unit 201 equipped with business phone control functionality, and can perform functions as a general business phone main unit in addition to edge computer functionality.
[0029] The business phone main unit 10 includes a power line L1, a business phone control / voice signal line L2, an Ethernet signal line L3, an L2 switch 102, a socket 107 for the OA unit, and a socket 108 for the container unit.
[0030] An OA unit 201, a board-shaped hardware device on which business phone functions and other features are implemented, is detachably connected to the OA unit socket 107. The power lines L1 and business phone control / voice signal lines L2 of the OA unit 201 and the motherboard 101 are interconnected via the OA unit socket 107.
[0031] Each container unit socket 108 is connected to a board-shaped container unit 202 that provides the container environments 2022 and 2028, and the power lines L1 and Ethernet signal lines L3 of the container unit 202 and motherboard 101 are interconnected via each container unit socket 108.
[0032] The signal line L3 may be independently wired without going through the socket 108 for each container unit, in which case the L2 switch 102 does not need to be mounted on the motherboard 101. Alternatively, each container unit 202 may be equipped with an L2 switch, and wired connections may be made via each L2 switch.
[0033] Each container unit 202 is equipped with its own hardware resources, including a CPU, memory, storage, various accelerators, and an operating system, enabling it to independently perform server and computer functions.
[0034] In this embodiment, the container unit 202 is managed and controlled by an open platform container orchestration tool, and includes a master unit 202m that operates as the master node of the container orchestration tool and a worker unit 202w that operates as a worker node of the container orchestration tool.
[0035] Figure 2 is a functional block diagram schematically showing the configuration of the main parts of the master unit 202m and the worker unit 202w. In this embodiment, the case in which one container unit 202 operates as one node is explained as an example, but if the processing capacity of each container unit 202 is sufficiently high, one container unit 202 can be operated as both a master node and a worker node, or one container unit 202 can be operated as multiple worker nodes.
[0036] The master unit 202m and worker unit 202w are equipped with unit initialization units 2021 and 2027, respectively, and integrated management / control is achieved through container application tools, making it possible to easily deploy, run, manage, and schedule applications, thereby reducing the burden on users.
[0037] The master node of the container orchestration tool (master unit 202m in this embodiment) is responsible for managing the state of each worker node (worker unit 202w in this embodiment) and sending instructions to the worker unit 202w to enter a predefined state. The worker unit 202w is responsible for setting its own node state in response to instructions from the master unit 202m.
[0038] In addition to its function as a master node, the master unit 202m has the function of deploying a configuration / deployment application 2023, an application management application 2024, a unit management application 2025, and a service advertisement application 2026 as a unique application 2029 for managing the entire system during initialization by the master unit initialization unit 2021 (step S105 described later).
[0039] Furthermore, since the deployed custom application 2029 is managed by a container orchestration tool, if worker unit 202w exists, it does not necessarily have to run on master unit 202m.
[0040] Each application can be operated by the administrator via the API of the unique application 2029 or the configuration / deployment application 2023 on the browser of the end-user terminal 2. Each node implements a container image containing user applications (apps A, B, etc.) and their corresponding libraries, which are downloaded from the container image distribution server 3 by the container runtime according to the instructions of the container orchestration tool. These operations can also be performed by the administrator calling the application management application 2024 from the configuration / deployment application 2023 running on the browser of the end-user terminal 2.
[0041] Worker unit 202w has multiple container environments 2028 implemented. Each container environment 2028 implements user applications (apps C, D, etc.) and their corresponding libraries.
[0042] The master unit 202m manages each container unit 202, which is implemented in the socket 108 for the container units, as a cluster, and each user application is controlled and managed by the coordinated operation of the container orchestration tool.
[0043] The master unit 202m and the worker unit 202w can have the same hardware configuration, in which case only the behavior of the unit initialization units 2021 and 2027 and the container orchestration tool will differ. Alternatively, the entire configuration, including the implemented applications, may be identical, and the units may be selectively operated as either the master unit 202m or the worker unit 202w by switching physical switches provided for each unit.
[0044] Figure 3 is a flowchart showing an example of the procedure by which the master unit initialization unit 2021 initializes the master unit 202m, which is initiated when the master unit 202m is first installed in the container unit socket 108, or when the power is subsequently turned on again.
[0045] In step S101, the various devices implemented in master unit 202m are initialized. In step S102, the OS implemented in master unit 202m is started. In step S103, IP addresses are assigned to the devices of master unit 202m. IP addresses can be dynamically assigned using DHCP or fixedly assigned using a configuration tool. In step S104, the container orchestration tool is started. In step S105, the application management application 2024, unit management application 2025, service advertisement application 2026, and configuration / deployment application 2023 are deployed, and initialization is completed.
[0046] Figure 4 is a flowchart showing an example of the procedure by which the worker unit initialization unit 2027 initializes the worker unit 202w. This procedure is initiated when the worker unit 202w is first installed in the container unit socket 108, or when the power is subsequently restored.
[0047] In step S201, the devices implemented in worker unit 202w are initialized. In step S202, the OS implemented in worker unit 202w is started. In step S203, an IP address is assigned to the devices of worker unit 202w.
[0048] In step S204, it is determined whether the unit is already registered with the master unit 202m. If it is registered, the process proceeds to step S207. If it is not registered, the process proceeds to step S205 to search for the master unit 202m. In step S206, the unit registers itself with the discovered master unit 202m. In step S207, a connection request is sent to connect the unit to the master unit 202m.
[0049] Thus, according to this embodiment, each worker unit 202w is equipped with a worker unit initialization unit 2027. When a worker unit 202w is first installed in the container unit socket 108 or when power is restored, it determines whether or not it is already registered with the master unit 202m. If it is not already registered, it automatically performs new registration with the master unit 202m. Therefore, users can easily build a highly available system in which they can freely install applications.
[0050] Figure 5 is a processing flowchart illustrating the operation of the unit management application 2025 on master unit 202m, and in particular, shows the cluster configuration procedure.
[0051] In step S301, if the worker unit 202w detects the connection request sent in step S207, the legitimacy of the request is verified in step S302. If the legitimacy is verified, the process proceeds to step S303, and the worker unit 202w is added to the cluster. If a disconnection request from the worker unit 202w is detected in step S304, the process proceeds to step S305, and the worker unit 202w is removed from the cluster.
[0052] Thus, according to this embodiment, the master unit 202m is equipped with a master node, and when it detects a connection request from the worker unit 202w, it automatically verifies the legitimacy of the request and adds or removes it from the cluster, making it possible to build and manage the cluster without requiring specialized knowledge or operation. In addition, from this point onward, the worker unit 202w is placed under the management of the master node of the container orchestration tool, so that functionality can continue to be provided even in the event of accidental hardware failures or maintenance.
[0053] Figure 6 shows the processing flow of the application management application 2024 implemented in the container orchestration tool of master unit 202m.
[0054] The application management application 2024 waits in preparation for API requests, and in step S401, when it detects an application deployment request from the end-user terminal 2 operating the configuration / deployment application 2023, it proceeds to step S402 to perform license authentication. In this embodiment, a public-key cryptography method is used for license authentication, and license authentication is performed based on whether or not a file signed with a pre-distributed private key can be verified with the public key.
[0055] Upon successful license authentication, the process proceeds to step S403, where the container image and various settings are downloaded from the container image distribution server 3. In step S404, the downloaded container image and various settings are deployed to the designated container by the container orchestration tool. In step S405, the deployed application is started and begins operation.
[0056] Furthermore, if an application undeployment request is detected in step S406, the process proceeds to step S407, where the specified application is undeployed from the cluster. Also, if an application list request is detected in step S408, the process proceeds to step S409 to obtain a list of applications, and in step S410, the obtained application list is sent as a response to the requesting end-user terminal 2.
[0057] Figure 7 is a flowchart showing the procedure by which the service advertisement application 2026, implemented in the container orchestration tool of master unit 202m, performs name resolution using mDNS (Multicast Domain Name System), and Figure 8 is a diagram illustrating that sequence.
[0058] At time t1 in Figure 8, when the user searches for the desired application from end-user terminal 2, at time t2, a name resolution request for that application is sent via multicast to each unit.
[0059] In the master unit 202m, the service advertisement application 2026 receives the name resolution request at time t3, and when it detects this in step S501 in Figure 7, it proceeds to step S502. In step S502, the service advertisement application 2026 determines at time t4 whether the corresponding FQDN is registered. If the FQDN is registered, it proceeds to step S503, and at time t5, it sends the FQDN as a name resolution response to the requesting end-user terminal 2.
[0060] Thus, in this embodiment, when a user discovers an application, the name resolution request is multicast to each container unit 202 via mDNS, and only the service-advertising application 2026 on the master unit 202m automatically responds with the IP address of the application, making it easy to achieve name resolution in the local environment.
[0061] In the above embodiment, the present invention was described as an example in which an OA unit 201 that operates as a business phone unit is implemented on the edge computer device 1 to configure it as a business phone main unit 10 equipped with edge computer functionality. However, the present invention is not limited to this, and it may also be configured as a standalone edge computer device without additional functions as an OA device by implementing only the container unit 202. In that case, an application for a business phone main unit may be implemented on the container unit 202 to configure a business phone main unit that operates in a container environment.
[0062] Furthermore, by replacing the OA unit 201, which operates as a business phone unit implemented together with the container unit 202, with another OA unit capable of performing other OA functions (such as a copy unit capable of performing copying functions), a copier equipped with edge computing capabilities can be configured. Furthermore, by implementing OA units that perform scanning and printing functions, a multifunction device equipped with edge computing capabilities can be configured. [Explanation of symbols]
[0063] 1…Edge computer device, 2…End user terminal, 3…Container image distribution server, 10…Business phone main unit, 107…Socket for OA unit, 108…Socket for container unit, 201…OA unit, 202…Container unit, 202m…Master unit, 202w…Worker unit, 2021, 2027…Initialization unit, 2023…Configuration / deployment app, 2024…App management app, 2025…Unit management app, 2026…Service advertisement app, 2022, 2028…Container environment, 2029…Specific app, L1…Power line, L2…Business phone control / voice signal line, L3…Ethernet signal line
Claims
1. In an edge computer device running an application in a container environment managed by a container orchestration tool on a local network, A container unit that functions as a node to which a container environment is assigned, Each container unit is equipped with a socket for the container unit that allows for the insertion and removal of the hardware resources of the edge computer device. The container units connected to the aforementioned sockets for container units are managed as a cluster. At least one of the container units is a master unit, and the rest are worker units. The aforementioned container orchestration tool includes an API, The master unit and worker unit are operated via API from a user terminal on the local network. The edge computer device is characterized in that the worker unit, when connected to the socket for the container unit, is equipped with a unit initialization means that searches for a master unit and requests registration and connection to its own master unit.
2. The edge computer device according to claim 1, characterized in that the hardware resources and the power lines and Ethernet ports of the container unit are interconnected, and at least the power lines are connected by sockets for the container unit.
3. The edge computer device according to claim 1, characterized in that the container unit implements an application that causes the edge computer device to operate as an office automation device.
4. The edge computer device according to claim 1, characterized in that the container unit implements an application that causes the edge computer device to operate as a business phone main unit.
5. The aforementioned edge computer device also incorporates the functions of an office automation (OA) device. At least one OA unit that controls OA equipment, The edge computer device according to claim 1, further comprising sockets for OA units for connecting each OA unit to the hardware resources of the edge computer device.
6. The aforementioned office automation equipment also incorporates the functions of a business phone system. The aforementioned OA unit is a business phone unit that controls business phones, The edge computer device according to claim 5, characterized in that the hardware resources and the power lines and business phone-specific signal lines of each business phone unit are interconnected by the sockets for the OA units.
7. The edge computer device according to claim 1, characterized in that the container orchestration tool comprises a unit management means for adding a worker unit to a cluster in response to a connection request from the worker unit.
8. The edge computer device according to claim 1, characterized in that the container orchestration tool includes an application management means that performs license authentication for applications that have been requested to be deployed, and downloads the authenticated applications from the internet and deploys them to a predetermined container.
9. The edge computer device according to claim 1, characterized in that the container orchestration tool includes a service advertisement means that, upon receiving a name resolution request multicast from a user terminal on the local network, determines whether the corresponding FQDN is registered and returns a registered name resolution response.
Citation Information
Patent Citations
Private branch exchange, telephone set, and telephone system with them
JP2008259053A
Information management device and information management method
JP2015187867A
Edge system, control method edge system, computer program used to control edge system, and recording medium thereof
JP2021010130A
Device for machine tool
JP2023049230A
Virtual machine container apparatus, control method of virtual machine container, program, and recording medium
JP2023064327A
