WO2024176321A1

WO2024176321A1 - Management device, management method, and management program

Info

Publication number: WO2024176321A1
Application number: PCT/JP2023/006077
Authority: WO
Inventors: 勇樹武井; 諭士中務
Original assignee: 日本電信電話株式会社
Priority date: 2023-02-20
Filing date: 2023-02-20
Publication date: 2024-08-29

Abstract

In a management device (10), a storage unit (14) stores agent information DB (14a) that indicates information about each function to be processed, and device information DB (14b) that indicates information about each device to be processed. A determination unit (15b) determines, on the basis of the agent information DB (14a) and the device information DB (14b), whether or not a predetermined function can be deployed in a predetermined device (20). A registration unit (15c) registers a predetermined function to a device (20) determined as being capable of having said function deployed therein.

Description

Management device, management method, and management program

The present invention relates to a management device, a management method, and a management program.

In recent networks, in addition to traditional vendor-made network (NW, NetWork) devices, white box switches (hereafter referred to as white boxes) are being used, which allow users to freely select the functions they want to deploy. In order for carriers to add network functions, they need to deploy these functions in any number of NW devices within the network. Previously, technology has been disclosed that allows users to create their own network functions and deploy them in white boxes (see Non-Patent Document 1).

However, with conventional technology, it can be difficult to add network functions or change settings for any number of network devices within a network. For example, with conventional technology, it is necessary to determine whether an additional function can be installed, deploy the function, and activate it for each white box, which requires a significant amount of maintenance work.

The present invention was made in consideration of the above, and aims to make it easy to add network functions and change settings for any number of devices in a network.

In order to solve the above problems and achieve the objectives, the management device according to the present invention is characterized by having a storage unit that stores information about each function to be processed and information about each device to be processed, a determination unit that determines whether a specific function can be deployed to a specific device based on the information about each function to be processed and the information about each device to be processed, and a registration unit that registers the specific function to the device that has been determined to be able to deploy the function.

The present invention makes it easy to add network functions and change settings for any number of devices in a network.

FIG. 1 is a diagram for explaining an overview of a management device according to the present embodiment. FIG. 2 is a diagram for explaining an overview of the management device of this embodiment. FIG. 3 is a schematic diagram illustrating a schematic configuration of a management device according to the present embodiment. FIG. 4 is a diagram illustrating an example of the data structure of the agent information DB. FIG. 5 is a diagram illustrating an example of the data structure of the device information DB. FIG. 6 is a diagram for explaining the management process. FIG. 7 is a diagram for explaining the management process. FIG. 8 is a diagram for explaining the management process. FIG. 9 is a flowchart showing the management process procedure. FIG. 10 is a flowchart showing the management process procedure. FIG. 11 illustrates an example of a computer that executes a management program.

Below, one embodiment of the present invention will be described in detail with reference to the drawings. Note that the present invention is not limited to this embodiment. In addition, in the drawings, the same parts are denoted by the same reference numerals.

[Overview of the Management Device]
1 and 2 are diagrams for explaining an overview of the management device of this embodiment. The management device of this embodiment is a network controller (NW-CTL) 10 illustrated in FIG. 1, which adds or modifies network functions to required locations at the timing required by the carrier. For example, the management device 10 deploys agents that realize network functions at any location in the network and changes the settings of the agents. Specifically, the network controller 10 deploys/deactivates agents, changes settings, and controls agents for appropriate white boxes 20 (FIG. 1(2)), and manages the status of agent deployment (FIG. 1(1)).

This allows the management device 10 to easily deploy network functions such as those illustrated in FIG. 2 at appropriate locations within the network. For example, in the example shown in FIG. 2(a), a test function is deployed to multiple devices (node #1, node #2), and communication confirmation tests are performed between the deployed agents periodically or on-demand. In the example shown in FIG. 2(b), an information acquisition function is deployed to acquire information about the device (white box) and change the frequency and granularity of the acquired information, making it possible to detect abnormalities in the device to which the function is deployed. In the example shown in FIG. 2(c), value-added functions for user communications, such as security functions, filter functions, address conversion functions, and sorting functions, are deployed.

Note that the device to be processed in this embodiment is not limited to the white box 20, but may be a network device such as a router.

[Configuration of management device]
3 is a schematic diagram illustrating a schematic configuration of a management device of this embodiment. As illustrated in FIG. 3, the management device 10 of this embodiment is realized by a general-purpose computer such as a personal computer, and includes an input unit 11, an output unit 12, a communication control unit 13, a storage unit 14, and a control unit 15.

The input unit 11 is realized using input devices such as a keyboard and a mouse, and inputs various instruction information, such as starting processing, to the control unit 15 in response to input operations by an operator. The output unit 12 is realized by a display device such as a liquid crystal display, a printing device such as a printer, etc. For example, the output unit 12 displays the results of the management processing described below.

The communication control unit 13 is realized by a NIC (Network Interface Card) or the like, and controls communication between the control unit 15 and external devices via telecommunication lines such as a LAN (Local Area Network) or the Internet. For example, the communication control unit 13 controls communication between the control unit 15 and a management server that manages various types of information.

The storage unit 14 is realized by a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. The storage unit 14 stores in advance the processing programs that operate the management device 10 and data used during the execution of the processing programs, or stores them temporarily each time processing is performed. The storage unit 14 may be configured to communicate with the control unit 15 via the communication control unit 13.

In this embodiment, the storage unit 14 stores an agent information DB (Data Base) 14a, a device information DB 14b, agent materials 14c, a control scenario 14d, and the like, which are used in the management process described below. This information is acquired via the input unit 11 or via the communication control unit 13 from a management server that manages various information, prior to the management process described below, or during the management process, and stored in the storage unit 14. Note that this various information is not limited to being stored in the storage unit 14, and may be collected, for example, by the acquisition unit 15a described below when the management process is executed, and immediately transferred to a downstream functional unit.

Agent information DB14a shows information about each function to be processed. For example, agent information DB14a shows information about available models and other information related to the agent to be deployed.

Here, FIG. 4 is a diagram illustrating an example of the data configuration of the agent information DB. Specifically, as illustrated in FIG. 4, the agent information DB 14a includes the agent name, the vendor and version of the deployable model, the deployable usage type, and the amount of consumed resources. Here, the usage type refers to the usage form of the device within the network, and is, for example, any of Spine, Leaf, and UserSW.

In the example shown in Figure 4, for example, it is shown that the agent name "XXX function agent" is a deployable model vendor "Company A", the version is "OSver 1.0", and the deployable usage type is "Spine" or "Leaf".

The device information DB 14b shows information about each device to be processed. For example, the device information DB 14b shows resource information about the white box 20 to be processed. Here, FIG. 5 is a diagram illustrating an example of the data structure of the device information DB. As illustrated in FIG. 5, the device information DB 14b includes information such as the usage type, model information (vendor), version, address, resources, and available resource amount for each white box 20. In the example shown in FIG. 5, for example, for white box #1, the usage type "Spine", model information "Company A", and version "OS version 1.0" are shown.

In addition, device information DB14b contains information about deployed agents, their configuration status, and their operating status, which are updated in the management process described below.

The agent material 14c represents the functional agent to be deployed, and is the agent entity that is registered in each device by the management process described below. Here, Figs. 6 to 8 are diagrams for explaining the management process. For example, as illustrated in Fig. 6, the agent material 14c is transferred to each device to be processed by the registration unit 15c described below. Alternatively, each device to be processed acquires the agent material 14c in response to an instruction from the registration unit 15c.

The control scenario 14d is information that indicates the procedure for deploying an agent to each white box. For example, as shown in FIG. 6, the control scenario 14d specifies the deployment procedure for each agent function for each white box 20 vendor.

Returning to the explanation of FIG. 3, the control unit 15 is realized using a CPU (Central Processing Unit), NP (Network Processor), FPGA (Field Programmable Gate Array), etc., and executes processing programs stored in memory. As a result, the control unit 15 functions as an acquisition unit 15a, a judgment unit 15b, a registration unit 15c, and a setting unit 15d, as exemplified in FIG. 3, to execute management processing. Note that each of these functional units, or some of them, may be implemented in different hardware. The control unit 15 may also have other functional units.

The acquisition unit 15a accepts the designation of the function (agent) to be processed in the management process and the device (white box) 20 to be processed. For example, the acquisition unit 15a accepts input by the maintenance person via the input unit 11 or via the communication control unit 13 from the maintenance person's terminal, etc., of the agent to be deployed and information designating the device, such as the IP address of the device on which the agent is to be deployed, as exemplified in FIG. 6.

The determination unit 15b determines whether a specific function can be deployed to a specific device based on the agent information DB (14a) and the device information DB (14b). For example, as illustrated in FIG. 7, the management device 10 includes an agent information DB 14a and a device information DB 14b, and the agents that can be deployed for each device model and type of use are managed by combining these pieces of information.

Then, the judgment unit 15b judges whether or not the specified agent can be deployed in the specified white box 20. Specifically, the judgment unit 15b judges whether or not the agent can be deployed in the white box 20, that is, whether or not the combination of the agent and the white box 20 is appropriate, and if so, whether or not the resources of the white box 20 are sufficient.

The registration unit 15c registers a specific functional agent in a white box 20 that has been determined to be capable of deploying the agent. For example, the registration unit 15c registers the agent in the white box 20 according to a specific control scenario 14d. That is, the registration unit 15c instructs the white box 20 to register the agent materials 14c corresponding to the agent in accordance with the control scenario 14d that indicates the registration processing procedure for the agent for the vendor of the white box 20.

In this case, as described above, the registration unit 15c may transfer the agent materials 14c of the agent to the white box 20. Alternatively, the white box 20 may directly access the agent materials 14c and obtain the agent materials 14c corresponding to the agent.

The registration unit 15c also adds information about the registered function to the device information DB 14b. For example, as illustrated in FIG. 7, the registration unit 15c adds the deployed agent to the information about the white box 20 in the device information DB 14b. In the example shown in FIG. 7, for white box #1, the deployed agent "XXXX function agent" is added to the device information DB 14b.

The setting unit 15d sets the registered functions in the device so that they can be executed. For example, as shown in FIG. 8, the setting unit 15d sets information such as parameters and config required for operation for the deployed agent. The setting unit 15d also controls the instruction to start and end operation. In doing so, the setting unit 15d accepts input from the maintenance person instructing the setting and start/end of operation together with information specifying the device such as an IP address via the input unit 11 or from the maintenance person's terminal via the communication control unit 13.

The setting unit 15d also adds information about the set function to the device information DB 14b. For example, as illustrated in FIG. 8, the setting unit 15d adds information about the setting status and operation status to the information about the white box 20 in the device information DB 14b. In the example shown in FIG. 8, the setting status of white box #1 has been updated to "completed" and the operation status to "operating."

In this way, the management device 10 can easily add and manage function agents for the white boxes 20 to which service functions are deployed. Therefore, even if there are multiple white boxes 20 to be processed, it is easy to add and manage function agents.

[Management process]
Next, the management process by the management device 10 according to the present embodiment will be described with reference to Fig. 9 and Fig. 10. Fig. 9 and Fig. 10 are flowcharts showing the management process procedure. First, Fig. 9 illustrates a registration process procedure for deployment. The flowchart in Fig. 9 starts, for example, when a user performs an operation input to instruct the start of the process.

First, the acquisition unit 15a accepts the specification of the function (agent) to be processed in the registration process and the device (white box) 20 to be processed (step S1).

The judgment unit 15b judges whether an agent can be deployed in the white box 20, i.e., whether the combination of the agent and the white box 20 is appropriate, and if so, whether the resources of the white box 20 are sufficient, based on the agent information DB (14a) and the device information DB (14b).

If the determination unit 15b determines that the information is valid (Yes in step S2), the process proceeds to step S3. On the other hand, if the determination unit 15b determines that the information is not valid (No in step S2), the process ends.

In the process of step S3, the registration unit 15c registers a specific functional agent to the white box 20 that has been determined to be capable of deploying the agent. For example, the registration unit 15c registers the agent to the white box 20 according to a specific control scenario 14d.

The registration unit 15c also adds the registered deployed agent to the information of the white box 20 in the device information DB 14b, and updates the device information DB 14b (step S4). This completes the series of registration processes.

Next, FIG. 10 illustrates an example of a configuration process for configuring deployed functions. The flowchart in FIG. 10 starts, for example, when a user performs an operation input to start the process.

First, the acquisition unit 15a accepts the specification of the function (agent) to be processed in the configuration process and the device (white box) 20 to be processed (step S11).

Next, the setting unit 15d sets information such as parameters and configuration required for operation so that the agent already deployed in the target white box 20 can be executed (step S12).

The setting unit 15d also adds information about the setting status, operation status, etc. of the set function to the information about the white box 20 in the device information DB 14b, and updates the device information DB 14b (step S13). This completes the series of setting processes.

[effect]
As described above, in the management device 10 of this embodiment, the storage unit 14 stores the agent information DB 14a indicating information on each function to be processed, and the device information DB 14b indicating information on each device to be processed. The determination unit 15b determines whether or not a predetermined function can be deployed in a predetermined device based on the agent information DB (14a) and the device information DB (14b). The registration unit 15c registers the function for the device 20 determined to be able to deploy the predetermined function.

Specifically, the registration unit 15c registers functions to the device 20 according to a predetermined control scenario 14d.

This allows the management device 10 to easily add function agents to the white boxes 20 on which service functions are to be deployed. Therefore, even if there are multiple white boxes 20 to be processed, function agents can be easily added. In this way, the management device 10 makes it easy to add network functions and change settings for any number of devices within the network.

The registration unit 15c also adds the registered function information to the device information DB 14b, which indicates information about each device to be processed. This enables the management device 10 to manage the status of function deployment within the network.

The setting unit 15d also sets the functions registered in the device 20 to be executable. This makes it easy to change the settings of the network functions.

The setting unit 15d adds information about the set function to the device information DB 14b, which shows information about each device to be processed. This also enables the management device 10 to manage the status of function deployment within the network.

[program]
A program in which the process executed by the management device 10 according to the above embodiment is written in a language executable by a computer can also be created. As an embodiment, the management device 10 can be implemented by installing a management program that executes the above management process as package software or online software on a desired computer. For example, the information processing device can function as the management device 10 by executing the above management program on an information processing device. The information processing device here includes desktop or notebook personal computers. In addition, the information processing device also includes mobile communication terminals such as smartphones, mobile phones, and PHS (Personal Handyphone System), as well as slate terminals such as PDAs (Personal Digital Assistants). The functions of the management device 10 may also be implemented on a cloud server.

FIG. 11 is a diagram showing an example of a computer that executes a management program. The computer 1000 has, for example, a memory 1010, a CPU 1020, a hard disk drive interface 1030, a disk drive interface 1040, a serial port interface 1050, a video adapter 1060, and a network interface 1070. These components are connected by a bus 1080.

The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012. The ROM 1011 stores a boot program such as a BIOS (Basic Input Output System). The hard disk drive interface 1030 is connected to a hard disk drive 1031. The disk drive interface 1040 is connected to a disk drive 1041. A removable storage medium such as a magnetic disk or optical disk is inserted into the disk drive 1041. The serial port interface 1050 is connected to a mouse 1051 and a keyboard 1052, for example. The video adapter 1060 is connected to a display 1061, for example.

Here, the hard disk drive 1031 stores, for example, an OS (Operating System) 1091, an application program 1092, a program module 1093, and program data 1094. Each piece of information described in the above embodiment is stored, for example, in the hard disk drive 1031 or memory 1010.

The management program is stored in the hard disk drive 1031, for example, as a program module 1093 in which commands to be executed by the computer 1000 are written. Specifically, the program module 1093 in which each process executed by the management device 10 described in the above embodiment is written is stored in the hard disk drive 1031.

In addition, data used for information processing by the management program is stored as program data 1094, for example, in the hard disk drive 1031. Then, the CPU 1020 reads the program module 1093 and program data 1094 stored in the hard disk drive 1031 into the RAM 1012 as necessary, and executes each of the procedures described above.

The program module 1093 and program data 1094 related to the management program are not limited to being stored in the hard disk drive 1031, but may be stored in a removable storage medium, for example, and read by the CPU 1020 via the disk drive 1041 or the like. Alternatively, the program module 1093 and program data 1094 related to the management program may be stored in another computer connected via a network, such as a LAN or WAN (Wide Area Network), and read by the CPU 1020 via the network interface 1070.

The above describes an embodiment of the invention made by the inventor, but the present invention is not limited to the descriptions and drawings that form part of the disclosure of the present invention according to this embodiment. In other words, other embodiments, examples, operational techniques, etc. made by those skilled in the art based on this embodiment are all included in the scope of the present invention.

REFERENCE SIGNS LIST 10 Management device 11 Input unit 12 Output unit 13 Communication control unit 14 Storage unit 14a Agent information DB
14b Device information DB

14c Agent material

14d Control scenario 15 Control unit

15a Acquisition unit

15b Determination unit

15c Registration unit

15d Setting unit 20 White box (device)

Claims

a storage unit that stores information regarding each function to be processed and information regarding each device to be processed;
a determination unit that determines whether a predetermined function can be deployed in a predetermined device based on information about each function of the processing target and information about each device of the processing target;
a registration unit that registers the function in the device that is determined to be capable of deploying the predetermined function;
A management device comprising:
The management device according to claim 1, characterized in that the registration unit registers the functions to the device according to a predetermined scenario.
The management device according to claim 1, characterized in that the registration unit adds the registered information of the function to information about each of the devices.
The management device according to claim 1, further comprising a setting unit that sets the functions registered in the device to be executable.
The management device according to claim 4, characterized in that the setting unit adds information about the set function to information about each of the devices.
A management method executed by a management device, comprising:
the management device has a storage unit that stores information about each function to be processed and information about each device to be processed;
a determination step of determining whether a predetermined function can be deployed in a predetermined device based on information about each function to be processed and information about each device to be processed;
a registration step of registering the function in the device determined to be capable of installing the predetermined function;
A management method comprising the steps of:
a determination step of referring to a storage unit that stores information on each function to be processed and information on each device to be processed, and determining whether or not a predetermined function can be deployed in a predetermined device based on the information on each function to be processed and the information on each device to be processed;
a registration step of registering the function in the device determined to be capable of deploying the predetermined function;
A management program for running the following on a computer.