WO2022003926A1 - Management device, management method, management program, and management system - Google Patents

Management device, management method, management program, and management system Download PDF

Info

Publication number
WO2022003926A1
WO2022003926A1 PCT/JP2020/026106 JP2020026106W WO2022003926A1 WO 2022003926 A1 WO2022003926 A1 WO 2022003926A1 JP 2020026106 W JP2020026106 W JP 2020026106W WO 2022003926 A1 WO2022003926 A1 WO 2022003926A1
Authority
WO
WIPO (PCT)
Prior art keywords
management
request
config
communication device
unit
Prior art date
Application number
PCT/JP2020/026106
Other languages
French (fr)
Japanese (ja)
Inventor
宏樹 岩橋
貴之 藤原
裕太 渡辺
貴博 柴田
Original Assignee
日本電信電話株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 日本電信電話株式会社 filed Critical 日本電信電話株式会社
Priority to JP2022532974A priority Critical patent/JP7439928B2/en
Priority to PCT/JP2020/026106 priority patent/WO2022003926A1/en
Publication of WO2022003926A1 publication Critical patent/WO2022003926A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/0806Configuration setting for initial configuration or provisioning, e.g. plug-and-play
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08Configuration management of networks or network elements
    • H04L41/0803Configuration setting
    • H04L41/084Configuration by using pre-existing information, e.g. using templates or copying from other elements
    • H04L41/0843Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00Arrangements for monitoring or testing data switching networks
    • H04L43/08Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning

Definitions

  • the present invention relates to a management device, a management method, a management program, and a management system.
  • a centralized management server inputs a config when a new user input request is generated from a higher-level system.
  • the centralized management server appropriately determines the communication device that accommodates the user, that is, the target to which the config is input, according to the amount of free resources of each communication device.
  • FIG. 9 is a diagram showing the configuration of a conventional management system.
  • the centralized management server receives a config input request for accommodating a user from a higher-level system (101).
  • the centralized management server appropriately determines the communication device in which the corresponding user is accommodated according to the amount of free resources of each communication device (102).
  • the centralized management server executes the config input of the corresponding user to the communication device of the determined accommodation destination (103).
  • the communication of the corresponding user is established on the communication device to which the configuration is input (104).
  • the conventional method has a problem that it may be difficult to ensure redundancy and extensibility.
  • scaling up the centralized management server has the problem that it is necessary to stop the system at the time of implementation.
  • the management device includes a storage unit for storing the request contents of the config input for a plurality of communication devices accommodating the users who use the network, the request contents, and the request contents. Based on the availability of resources of the plurality of communication devices, the communication device for executing the config input is determined from the plurality of communication devices, and the identification information for identifying the determined communication device is set in the request content. It has a determination unit that is associated and stored in the storage unit, and an execution unit that executes config input based on the request content for a communication device identified by the identification information associated with the request content. It is characterized by.
  • FIG. 1 is a diagram showing a configuration example of the management system of the first embodiment.
  • FIG. 2 is a diagram illustrating a method of determining a storage position.
  • FIG. 3 is a diagram illustrating a method of inputting a config.
  • FIG. 4 is a diagram illustrating a resource control method.
  • FIG. 5 is a diagram illustrating a priority control method.
  • FIG. 6 is a diagram illustrating the effect of the first embodiment.
  • FIG. 7 is a sequence diagram showing a processing flow of the management system of the first embodiment.
  • FIG. 8 is a diagram showing an example of a computer that executes a management program.
  • FIG. 9 is a diagram showing the configuration of a conventional management system.
  • FIG. 1 is a diagram showing a configuration example of the management system of the first embodiment.
  • the management system 20 receives a config input request from the host system 10.
  • the function of the host system 10 may be realized by an operator. In that case, the operator inputs the content of the config input request to the management system 20.
  • Input of the config is to set the communication device accommodating the user according to the opening, changing, cancellation, etc. of the service.
  • the management system 20 includes an upper system corresponding unit 201, a config input request management DB 202, a device management DB 203, a device management unit 204, a resource controller 205, a device control unit 210, a device control unit 220, and a device control unit. It has 230.
  • the management system 20 may be realized by a plurality of computers or may be realized as a management device by one computer.
  • Each of the host system corresponding unit 201, config input request management DB 202, device management DB 203, device management unit 204, resource controller 205, device control unit 210, device control unit 220, and device control unit 230 is realized by a physical machine or a virtual machine. Will be done.
  • the management system 20 has a communication device 211, a communication device 212, and a communication device 213 assigned to the device control unit 210. Further, the management system 20 has a communication device 221, a communication device 222, and a communication device 223 assigned to the device control unit 220. Further, the management system 20 has a communication device 231, a communication device 232, and a communication device 233 assigned to the device control unit 210.
  • the communication device is a switch, a router, or the like, and accommodates a user who uses a communication service.
  • the host system corresponding unit 201 receives a config input request from the host system 10 (1).
  • the device management unit 204 periodically monitors the config input request management DB 202, confirms the vacant accommodation position, and determines the accommodation position (2).
  • the host system corresponding unit 201 registers the received config input request in the config input request management DB 202 (3).
  • the config input request management DB 202 stores the contents of the config input request for the plurality of communication devices accommodating the users who use the network.
  • the config input request management DB 202 is an example of a storage unit.
  • the device management unit 204 periodically monitors the config input request management DB 202, and when it confirms that the config input request has been registered, acquires the request content of the config input request (4). Further, the device management unit 204 determines a communication device for executing config input from a plurality of communication devices based on the request contents and the availability of resources of the plurality of communication devices, and determines the determined communication device. The information for identification is stored in the config input request management DB 202 in association with the request contents.
  • the device management unit 204 is an example of a determination unit.
  • the device control unit 210 executes config input based on the request content to the communication device identified by the identification information associated with the request content (5). As a result, communication between the communication device and the user is established (6).
  • the device control unit 210 is an example of an execution unit.
  • At least one of a plurality of communication devices is assigned to the device control unit 210.
  • the device control unit 210 is assigned the communication device 211, the communication device 212, and the communication device 213.
  • the device control unit 210 periodically monitors the config input request management DB 202 and acquires the request content associated with the identification information of the assigned communication device.
  • the device control unit 220 and the device control unit 230 also perform the same processing as the device control unit 210.
  • the communication device 211 accommodates the users U11 and U12 via the L2 network N.
  • the communication device may be assigned to a plurality of device control units or may be assigned to a single device control unit.
  • the communication device 223 is assigned to both the device control unit 220 and the device control unit 230.
  • the communication device 221 is assigned only to the device control unit 220.
  • each of the plurality of device control units periodically monitors the config input request management DB2 and is associated with the identification information of the communication device assigned to one or more of the plurality of device control units. Get the request content.
  • FIG. 2 is a diagram illustrating a method of determining a storage position.
  • the scenario prepared in advance according to the config contents is stored in the device management DB 203.
  • the scenario shall be prepared according to the type of communication service, the number of users, the amount of communication, etc. indicated by the content of the request.
  • the device management unit 204 acquires the request content from the config input request management DB 202 (2-1). Then, the device management unit 204 selects a scenario according to the content of the request (2-2). Further, the device management unit 204 confirms the free resources of each communication device and determines the accommodation position (2-3).
  • the accommodation position means the communication device to which the config is input. In this way, the device management unit 204 determines the communication device for executing the config input according to the scenario corresponding to the request content prepared in advance.
  • FIG. 3 is a diagram illustrating a method of inputting a config.
  • the device control unit 210 executes a command obtained by substituting a predetermined parameter included in a template of a command for inputting a config prepared in advance based on a request content and identification information.
  • the template file for creating the template is stored in the device management DB 203.
  • the device control unit 210 prepares a template file for each model of the communication device and the content of the input request, replaces the variable parameters in the template file, and generates a command list to be input to the device.
  • the parameter is a variable item for each user, and is, for example, an address, a user identifier, a communication band, a charge, and the like.
  • the command template file may be different depending on whether the input of the config is opening, changing, or canceling the service, and the organization to which the user belongs (company A, company B, etc.).
  • the device control unit 210 first selects a config template (5-1). Next, the device control unit 210 creates a command list (5-2). Then, the device control unit 210 executes the created command and inputs the config (5-3).
  • the processing of the resource controller 205 will be described with reference to FIGS. 4 and 5.
  • the resource controller 205 monitors the operation status of each functional unit including the device control unit 210, the device control unit 220, and the device control unit 230, and controls the operation of each functional unit according to the status.
  • the resource controller 205 adjusts the resources assigned to each functional unit, the priority of the task, and the like.
  • the resource controller 205 is an example of an adjustment unit.
  • FIG. 4 is a diagram illustrating a resource control method.
  • the resource controller 205 monitors the number of input requests received at regular intervals, allocates resources in the device control unit according to the number, and changes the confirmation frequency of the config input request management DB 202 in periodic monitoring. It is possible to prevent the request from staying.
  • FIG. 4 is a diagram illustrating a resource control method. As shown in FIG. 4, first, the resource controller 205 refers to the config input request management DB 202 and confirms the number of input requests waiting to be processed (7). Then, the resource controller 205 scales up according to the number of input requests, allocates compute resources, and changes the DB confirmation frequency (8).
  • the resource controller 205 temporarily expands the device control unit 210a, and allocates the communication device 211, the communication device 212, and the communication device 213 to the added device control unit 210a.
  • the resource controller 205 may be expanded by automatically generating a virtual machine on a predetermined server. Further, the resource controller 205 may control only the device control unit (8) that needs to accelerate the confirmation frequency among the plurality of device control units.
  • the resource controller 205 determines the resources allocated to the device control unit 210 and the monitoring frequency of the config input request management DB 202 by the device control unit 210 based on the number of unprocessed request contents stored in the config input request management DB 202. adjust. As a result, the resource controller 205 can prevent the access resource of the input request management DB 202 from being exhausted because the access frequency to the input request management DB 202 of the device control unit is too high.
  • FIG. 5 is a diagram illustrating a priority control method.
  • the resource controller 205 gives priority to the config input based on the request content whose residence time is a certain time or more among the unprocessed request contents stored in the config input request management DB 202, and the device control unit 210. Can be processed.
  • the resource controller 205 confirms whether there is an input request (which has not been processed for a certain period of time or longer) during the stagnation (9). Then, the resource controller 205 sets the priority of the input request during the stagnation high (10). As a result, the stagnation of the config input request is eliminated.
  • FIG. 6 is a diagram illustrating the effect of the first embodiment.
  • the management system 20 makes it possible to carry out appropriate expansion according to the characteristics of each functional unit by distributing the functions. For example, the device control unit can be expanded by scaling out, and the other functional units can be expanded by scaling up. Further, in the management system 20, the easiness of remodeling due to the addition of a new service, the renewal of the device, etc. is guaranteed by creating a scenario for determining the accommodation position and creating a template for inputting the config.
  • FIG. 7 is a sequence diagram showing a processing flow of the management system of the first embodiment.
  • the host system corresponding unit 201 receives a config input request from the host system 10 (step S101).
  • the host system corresponding unit 201 writes the received config input request to the config input request management DB 202 (step S102).
  • a record as shown in 202a is written in the config input request management DB 202.
  • the status of the config input request is "accepted”.
  • the host system correspondence unit 201 makes a reception response to the host system 10 (step S103).
  • the item called the execution function unit of the config input request management DB 202 holds information that identifies the function unit (the function unit that is executing or is waiting to be executed) that processes the next config input request.
  • Each function unit acquires a config input request to be processed from the config input request management DB 202 based on the information held in the item of the execution function unit.
  • the functional unit that next processes the config input request is the "device management unit".
  • the config input request shown in 202a is acquired by the device management unit, but is not acquired by the device control unit and the host system corresponding unit.
  • the device management unit 204 periodically attempts to acquire a request for which the expropriation position has not been determined from the config input request management DB 202 (steps S104 and S105). Here, the device management unit 204 selects a scenario for determining the accommodation position when the request for determining the acquisition position can be acquired (if applicable) (step S106).
  • the device management unit 204 estimates the resource consumption in the configuration input of the corresponding user (step S107). Further, the device management unit 204 confirms the remaining resources of each communication device (step S108). At this time, the device management unit 204 communicates with each communication device and collects information depending on the confirmation content. Then, the device management unit 204 determines the accommodating device according to the scenario (step S109). Here, the device management unit 204 writes the determined accommodation position in the config input request management DB 202 (step S110).
  • the accommodation position "# 1-1" is written in the config input request management DB 202, and the state is updated to "position determined".
  • "# 1-1" is identification information for identifying the communication device 211.
  • items such as user ID, service used, request type, etc. correspond to the request contents.
  • the functional unit that next processes the config input request is the “device control unit”.
  • the device control unit 210 acquires a request whose expropriation position is a subordinate communication device from the config input request management DB 202 (step S111).
  • the subordinate communication device means a communication device assigned to each device control unit.
  • the communication device 211, the communication device 212, and the communication device 213 are communication devices under the device control unit 210.
  • the device control unit 210 selects a command template according to the request content (step S112). Further, the device control unit 210 generates a command list based on the selected command template (step S113). Then, the device control unit 210 executes a command to the subordinate communication device 211 to set the configuration (step S114).
  • the device control unit 210 writes the setting completion to the config input request management DB 202 (step S115).
  • the status of the config input request management DB 202 is updated to "setting completed”.
  • the functional unit that next processes the config input request is the "upper system corresponding unit”.
  • the upper system corresponding unit 201 confirms the setting completion request in the config input request management DB 202 (step S116). Specifically, the host system corresponding unit 201 confirms that the status of the config input request management DB 202 is "setting completed”. Then, the host system corresponding unit 201 notifies the host system 10 of the completion of the setting (step S117).
  • the config input request management DB 202 stores the contents of the config input request for the plurality of communication devices accommodating the users who use the network.
  • the device management unit 204 determines a communication device to execute config input from a plurality of communication devices based on the request contents and the availability of resources of the plurality of communication devices, and identifies the determined communication device. The information for this is stored in the config input request management DB 202 in association with the request contents.
  • the device control unit 210 executes config input based on the request content to the communication device identified by the identification information associated with the request content.
  • the management system 20 divides the functional unit into each processing unit, and each functional unit autonomously acquires information from the config input request management DB 202 and executes processing according to the status of each input request.
  • the processing result is recorded in the config input request management DB 202.
  • the management system 20 by subdividing the entire processing into each functional part, it is possible to appropriately expand the performance for each processing, and even if one of the functional parts fails, the other parts continue to work. Can be continued.
  • the processing that was performed in the processing of the failed functional part can be restarted from the previous state at low cost by re-reading the DB state after recovery or from the redundant functional part.
  • another same functional unit or a redundant system can easily take over the processing.
  • redundancy and expandability in the system for managing the users of the communication service are guaranteed.
  • the management system 20 it is not necessary to specify the cooperative operation of each part as compared with the method in which each functional part instructs the processing of the next functional part, and the development and the modification of the functional part become easy. Specifically, some processing such as introduction of a new model of communication device, OS update, IF update for inputting config to communication device by adding new service, change / addition of accommodation position determination scenario, etc. hardly assumed. In such a case, the management system 20 can minimize the influence of the modification of some processes on other processes.
  • the management system 20 depending on the addition / change contents of the accommodation position determination scenario, additional information can be referred from the external DB or the system, the external scenario can be read, or special instructions (requests) can be given to the request contents from the host system. It is possible to easily deal with complicated modifications such as prioritizing, specifying the accommodation position and the accommodation position determination scenario, specifying the config command, etc.).
  • the device management unit 204 periodically monitors the config input request management DB 202 and acquires the request contents.
  • Each of the plurality of device control units periodically monitors the config input request management DB 202, and the request contents associated with the identification information of the communication device assigned to one or more of the plurality of device control units. get.
  • each functional unit monitors the shared config input request management DB 202, it is not necessary to exchange notifications with each other, and each functional unit can operate independently of each other.
  • the resource controller 205 adjusts the resources allocated to the device control unit 210 and the monitoring frequency of the config input request management DB 202 by the device control unit 210 based on the number of unprocessed request contents stored in the config input request management DB 202. As a result, the monitoring frequency can be suppressed, so that the amount of resources of the entire management system 20 can be suppressed even during peak hours.
  • the resource controller 205 causes the device control unit 210 to preferentially process the config input based on the request content whose residence time is a certain time or more among the unprocessed request contents stored in the config input request management DB 202. This makes it possible to prevent the config input request from staying.
  • the device management unit 204 determines the communication device for executing the config input according to the scenario according to the request content prepared in advance.
  • the device control unit 210 executes a command obtained by substituting a predetermined parameter included in a template of a command for inputting a config prepared in advance based on a request content and identification information. In this way, in the management system 20, processing can be streamlined by creating scenarios and templates.
  • each component of each of the illustrated devices is a functional concept, and does not necessarily have to be physically configured as shown in the figure. That is, the specific form of distribution and integration of each device is not limited to the one shown in the figure, and all or part of them may be functionally or physically dispersed or physically distributed in arbitrary units according to various loads and usage conditions. Can be integrated and configured. Further, each processing function performed by each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware by wired logic.
  • the management system 20 can be implemented by installing a management program that executes the above management process as package software or online software on a desired computer.
  • the information processing apparatus can function as the management system 20.
  • the information processing device referred to here includes a desktop type or notebook type personal computer.
  • information processing devices include smartphones, mobile communication terminals such as mobile phones and PHS (Personal Handyphone System), and slate terminals such as PDAs (Personal Digital Assistants).
  • the management system 20 can be implemented as a management server device in which the terminal device used by the user is a client and the service related to the above management process is provided to the client.
  • the management server device is implemented as a server device that receives a config input request as an input and provides a management service for inputting a config.
  • the management server device may be implemented as a Web server, or may be implemented as a cloud that provides services related to the above management processing by outsourcing.
  • FIG. 9 is a diagram showing an example of a computer that executes a management program.
  • the computer 1000 has, for example, a memory 1010 and a CPU 1020.
  • the computer 1000 also has 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. Each of these parts is connected by a bus 1080.
  • the memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012.
  • the ROM 1011 stores, for example, a boot program such as a BIOS (BASIC Input Output System).
  • BIOS BASIC Input Output System
  • the hard disk drive interface 1030 is connected to the hard disk drive 1090.
  • the disk drive interface 1040 is connected to the disk drive 1100.
  • a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1100.
  • the serial port interface 1050 is connected to, for example, a mouse 1110 and a keyboard 1120.
  • the video adapter 1060 is connected to, for example, the display 1130.
  • the hard disk drive 1090 stores, for example, the OS 1091, the application program 1092, the program module 1093, and the program data 1094. That is, the program that defines each process of the management device having the same function as the management system 20 is implemented as the program module 1093 in which the code that can be executed by the computer is described.
  • the program module 1093 is stored in, for example, the hard disk drive 1090.
  • the program module 1093 for executing the same processing as the functional configuration in the management device is stored in the hard disk drive 1090.
  • the hard disk drive 1090 may be replaced by an SSD.
  • the setting data used in the processing of the above-described embodiment is stored as program data 1094 in, for example, a memory 1010 or a hard disk drive 1090. Then, the CPU 1020 reads the program module 1093 and the program data 1094 stored in the memory 1010 and the hard disk drive 1090 into the RAM 1012 as needed, and executes the process of the above-described embodiment.
  • the program module 1093 and the program data 1094 are not limited to those stored in the hard disk drive 1090, but may be stored in, for example, a removable storage medium and read by the CPU 1020 via the disk drive 1100 or the like. Alternatively, the program module 1093 and the program data 1094 may be stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.). Then, the program module 1093 and the program data 1094 may be read from another computer by the CPU 1020 via the network interface 1070.
  • LAN Local Area Network
  • WAN Wide Area Network
  • N L2 network 10 Upper system 20 Management system 201 Upper system correspondence part 202 Config input request management DB 203 Device management DB 204 Device management unit 205 Resource controller 210, 220, 230 Device control unit 211, 212, 213, 211, 222, 223, 231, 232, 233 Communication device U11, U12 User

Abstract

According to the present invention, a configuration input request management DB (202) stores configuration input request contents, for a plurality of communication devices accommodating users who use a network. A device management unit (204) determines a communication device to execute configuration input from among the plurality of communication devices, on the basis of the request contents and the available status of resources of the plurality of communication devices, and stores information for identifying the determined communication device in the configuration input request management DB (202) in association with the request contents. A device control unit (210) executes configuration input based on the request contents, for the communication device identified by the identification information associated with the request contents.

Description

管理装置、管理方法、管理プログラム、及び管理システムManagement equipment, management methods, management programs, and management systems
 本発明は、管理装置、管理方法、管理プログラム、及び管理システム
に関する。
The present invention relates to a management device, a management method, a management program, and a management system.
 従来、ユーザへの通信サービスの提供において、上位システムからの新規ユーザの投入要求が発生した場合、集中管理サーバがコンフィグ投入を行う手法が知られている。その際、集中管理サーバは、各通信装置の空きリソース量に応じて、ユーザを収容する通信装置、すなわちコンフィグを投入する対象を適切に決定する。 Conventionally, in providing communication services to users, a method has been known in which a centralized management server inputs a config when a new user input request is generated from a higher-level system. At that time, the centralized management server appropriately determines the communication device that accommodates the user, that is, the target to which the config is input, according to the amount of free resources of each communication device.
 図9は、従来の管理システムの構成を示す図である。図9に示すように、集中管理サーバは、上位システムからユーザを収容するためのコンフィグ投入要求を受け取る(101)。ここで、集中管理サーバは、該当ユーザが収容される通信装置を、各通信装置の空きリソース量に応じて適切に決定する(102)。そして、集中管理サーバは、決定した収容先の通信装置に対し、該当ユーザのコンフィグ投入を実行する(103)。これにより、コンフィグ投入された通信装置上で該当ユーザの通信が確立される(104)。 FIG. 9 is a diagram showing the configuration of a conventional management system. As shown in FIG. 9, the centralized management server receives a config input request for accommodating a user from a higher-level system (101). Here, the centralized management server appropriately determines the communication device in which the corresponding user is accommodated according to the amount of free resources of each communication device (102). Then, the centralized management server executes the config input of the corresponding user to the communication device of the determined accommodation destination (103). As a result, the communication of the corresponding user is established on the communication device to which the configuration is input (104).
 しかしながら、従来の手法には、冗長性と拡張性を担保することが困難な場合があるという問題がある。 However, the conventional method has a problem that it may be difficult to ensure redundancy and extensibility.
 例えば、大量のコンフィグ投入要求を捌く必要が生じた場合、集中管理サーバの処理性能を向上させるスケールアップ、又は集中管理サーバの数を増加させるスケールアウトによって対応することが考えられる。 For example, when it becomes necessary to handle a large number of config input requests, it is conceivable to respond by scaling up to improve the processing performance of the centralized management server or scaling out to increase the number of centralized management servers.
 一方で、集中管理サーバのスケールアップには、実施の際にシステムを停止する必要があるという問題がある。また、集中管理サーバのスケールアウトでは、上位システムが複数の集中管理サーバにコンフィグ投入要求を投げ分けることが必要になること、及び、収容位置の競合や不整合等を生じさせることが問題になる。このように、従来の手法では、スケールアップやスケールアウトによる拡張性の担保が難しい場合がある。 On the other hand, scaling up the centralized management server has the problem that it is necessary to stop the system at the time of implementation. In addition, in the scale-out of the centralized management server, it becomes necessary for the host system to send the config input request to multiple centralized management servers, and it becomes a problem that the accommodation position conflicts and inconsistencies occur. .. As described above, it may be difficult to guarantee scalability by scale-up or scale-out with the conventional method.
 また、従来の手法のように、1つの集中管理サーバでコンフィグ投入に関する全ての処理を実現する場合、故障切替時に各投入要求の処理を切替先で引き継ぐには、常時処理状態を運用系と冗長系で共有しておく必要がある。このため、従来の手法では、冗長性を担保するためのコストが高くなる。 In addition, when all the processing related to config input is realized by one centralized management server as in the conventional method, in order to take over the processing of each input request at the switching destination at the time of failure switching, the constant processing state is redundant with the operation system. It is necessary to share it with the system. Therefore, in the conventional method, the cost for ensuring redundancy is high.
 上述した課題を解決し、目的を達成するために、管理装置は、ネットワークを利用するユーザを収容する複数の通信装置に対する、コンフィグ投入の要求内容を記憶する記憶部と、前記要求内容、及び、前記複数の通信装置のリソースの空き状況を基に、前記複数の通信装置の中からコンフィグ投入を実行する通信装置を決定し、当該決定した通信装置を識別するための識別情報を前記要求内容に対応付けて前記記憶部に格納する決定部と、前記要求内容に対応付けられた前記識別情報によって識別される通信装置に対し、前記要求内容に基づくコンフィグ投入を実行する実行部と、を有することを特徴とする。 In order to solve the above-mentioned problems and achieve the purpose, the management device includes a storage unit for storing the request contents of the config input for a plurality of communication devices accommodating the users who use the network, the request contents, and the request contents. Based on the availability of resources of the plurality of communication devices, the communication device for executing the config input is determined from the plurality of communication devices, and the identification information for identifying the determined communication device is set in the request content. It has a determination unit that is associated and stored in the storage unit, and an execution unit that executes config input based on the request content for a communication device identified by the identification information associated with the request content. It is characterized by.
 本発明によれば、通信サービスのユーザを管理するシステムにおける冗長性と拡張性を担保することができる。 According to the present invention, it is possible to ensure redundancy and expandability in a system that manages users of communication services.
図1は、第1の実施形態の管理システムの構成例を示す図である。FIG. 1 is a diagram showing a configuration example of the management system of the first embodiment. 図2は、収容位置の決定方法を説明する図である。FIG. 2 is a diagram illustrating a method of determining a storage position. 図3は、コンフィグの投入方法を説明する図である。FIG. 3 is a diagram illustrating a method of inputting a config. 図4は、リソースの制御方法を説明する図である。FIG. 4 is a diagram illustrating a resource control method. 図5は、優先度の制御方法を説明する図である。FIG. 5 is a diagram illustrating a priority control method. 図6は、第1の実施形態の効果を説明する図である。FIG. 6 is a diagram illustrating the effect of the first embodiment. 図7は、第1の実施形態の管理システムの処理の流れを示すシーケンス図である。FIG. 7 is a sequence diagram showing a processing flow of the management system of the first embodiment. 図8は、管理プログラムを実行するコンピュータの一例を示す図である。FIG. 8 is a diagram showing an example of a computer that executes a management program. 図9は、従来の管理システムの構成を示す図である。FIG. 9 is a diagram showing the configuration of a conventional management system.
 以下に、本願に係る管理装置、管理方法、管理プログラム、及び管理システムの実施形態を図面に基づいて詳細に説明する。なお、本発明は、以下に説明する実施形態により限定されるものではない。 Hereinafter, the management device, the management method, the management program, and the embodiment of the management system according to the present application will be described in detail based on the drawings. The present invention is not limited to the embodiments described below.
[第1の実施形態の構成]
 まず、図1を用いて、第1の実施形態に係る管理システムの構成を説明する。図1は、第1の実施形態の管理システムの構成例を示す図である。図1に示すように、管理システム20は、上位システム10からコンフィグ投入の要求を受け取る。なお、上位システム10の機能は、オペレータによって実現されてもよい。その場合、オペレータが管理システム20にコンフィグ投入要求の内容を入力する。コンフィグの投入とは、ユーザを収容する通信装置に対し、サービスの開通、変更、解約等にともなう設定を行うことである。
[Structure of the first embodiment]
First, the configuration of the management system according to the first embodiment will be described with reference to FIG. FIG. 1 is a diagram showing a configuration example of the management system of the first embodiment. As shown in FIG. 1, the management system 20 receives a config input request from the host system 10. The function of the host system 10 may be realized by an operator. In that case, the operator inputs the content of the config input request to the management system 20. Input of the config is to set the communication device accommodating the user according to the opening, changing, cancellation, etc. of the service.
 図1に示すように、管理システム20は、上位システム対応部201、コンフィグ投入要求管理DB202、装置管理DB203、装置管理部204、リソースコントローラ205、装置制御部210、装置制御部220及び装置制御部230を有する。 As shown in FIG. 1, the management system 20 includes an upper system corresponding unit 201, a config input request management DB 202, a device management DB 203, a device management unit 204, a resource controller 205, a device control unit 210, a device control unit 220, and a device control unit. It has 230.
 ここで、管理システム20は、複数のコンピュータにより実現されてもよいし、1つのコンピュータにより管理装置として実現されてもよい。上位システム対応部201、コンフィグ投入要求管理DB202、装置管理DB203、装置管理部204、リソースコントローラ205、装置制御部210、装置制御部220及び装置制御部230のそれぞれは、物理マシン又は仮想マシンにより実現される。 Here, the management system 20 may be realized by a plurality of computers or may be realized as a management device by one computer. Each of the host system corresponding unit 201, config input request management DB 202, device management DB 203, device management unit 204, resource controller 205, device control unit 210, device control unit 220, and device control unit 230 is realized by a physical machine or a virtual machine. Will be done.
 また、管理システム20は、装置制御部210に割り当てられた通信装置211、通信装置212及び通信装置213を有する。また、管理システム20は、装置制御部220に割り当てられた通信装置221、通信装置222及び通信装置223を有する。また、管理システム20は、装置制御部210に割り当てられた通信装置231、通信装置232及び通信装置233を有する。通信装置は、スイッチ及びルータ等であり、通信サービスを利用するユーザを収容する。 Further, the management system 20 has a communication device 211, a communication device 212, and a communication device 213 assigned to the device control unit 210. Further, the management system 20 has a communication device 221, a communication device 222, and a communication device 223 assigned to the device control unit 220. Further, the management system 20 has a communication device 231, a communication device 232, and a communication device 233 assigned to the device control unit 210. The communication device is a switch, a router, or the like, and accommodates a user who uses a communication service.
 まず、上位システム対応部201は、上位システム10からコンフィグ投入要求を受け取る(1)。ここで、装置管理部204は、定期的にコンフィグ投入要求管理DB202を監視し、空き収容位置確認及び収容位置決定を行うものとする(2)。上位システム対応部201は、受け取ったコンフィグ投入要求をコンフィグ投入要求管理DB202に登録する(3)。これにより、コンフィグ投入要求管理DB202は、ネットワークを利用するユーザを収容する複数の通信装置に対する、コンフィグ投入の要求内容を記憶する。コンフィグ投入要求管理DB202は、記憶部の一例である。 First, the host system corresponding unit 201 receives a config input request from the host system 10 (1). Here, the device management unit 204 periodically monitors the config input request management DB 202, confirms the vacant accommodation position, and determines the accommodation position (2). The host system corresponding unit 201 registers the received config input request in the config input request management DB 202 (3). As a result, the config input request management DB 202 stores the contents of the config input request for the plurality of communication devices accommodating the users who use the network. The config input request management DB 202 is an example of a storage unit.
 装置管理部204は、コンフィグ投入要求管理DB202を定期的に監視しつつ、コンフィグ投入要求が登録されたことを確認すると、コンフィグ投入要求の要求内容を取得する(4)。さらに、装置管理部204は、要求内容、及び、複数の通信装置のリソースの空き状況を基に、複数の通信装置の中からコンフィグ投入を実行する通信装置を決定し、当該決定した通信装置を識別するための情報を要求内容に対応付けてコンフィグ投入要求管理DB202に格納する。装置管理部204は、決定部の一例である。 The device management unit 204 periodically monitors the config input request management DB 202, and when it confirms that the config input request has been registered, acquires the request content of the config input request (4). Further, the device management unit 204 determines a communication device for executing config input from a plurality of communication devices based on the request contents and the availability of resources of the plurality of communication devices, and determines the determined communication device. The information for identification is stored in the config input request management DB 202 in association with the request contents. The device management unit 204 is an example of a determination unit.
 装置制御部210は、要求内容に対応付けられた識別情報によって識別される通信装置に対し、要求内容に基づくコンフィグ投入を実行する(5)。これにより、通信装置とユーザ間の通信が確立される(6)。装置制御部210は、実行部の一例である。 The device control unit 210 executes config input based on the request content to the communication device identified by the identification information associated with the request content (5). As a result, communication between the communication device and the user is established (6). The device control unit 210 is an example of an execution unit.
 装置制御部210は、複数の通信装置のうちの少なくともいずれかが割り当てられる。図1の例では、装置制御部210は、通信装置211、通信装置212及び通信装置213が割り当てられている。装置制御部210は、コンフィグ投入要求管理DB202を定期的に監視し、割り当てられた通信装置の識別情報に対応付けられた要求内容を取得する。なお、装置制御部220及び装置制御部230についても、装置制御部210と同様の処理を行う。例えば、通信装置211は、L2ネットワークNを介してユーザU11及びU12を収容する。 At least one of a plurality of communication devices is assigned to the device control unit 210. In the example of FIG. 1, the device control unit 210 is assigned the communication device 211, the communication device 212, and the communication device 213. The device control unit 210 periodically monitors the config input request management DB 202 and acquires the request content associated with the identification information of the assigned communication device. The device control unit 220 and the device control unit 230 also perform the same processing as the device control unit 210. For example, the communication device 211 accommodates the users U11 and U12 via the L2 network N.
 ここで、通信装置は、複数の装置制御部に割り当てられてもよいし、単一の装置制御部に割り当てられてもよい。図1の例では、通信装置223は、装置制御部220と装置制御部230の両方に割り当てられている。一方、通信装置221は、装置制御部220にのみ割り当てられている。このとき、複数の装置制御部のそれぞれは、コンフィグ投入要求管理DB2を定期的に監視し、複数の装置制御部のうちの1つ又は複数に割り当てられた通信装置の識別情報に対応付けられた要求内容を取得する。 Here, the communication device may be assigned to a plurality of device control units or may be assigned to a single device control unit. In the example of FIG. 1, the communication device 223 is assigned to both the device control unit 220 and the device control unit 230. On the other hand, the communication device 221 is assigned only to the device control unit 220. At this time, each of the plurality of device control units periodically monitors the config input request management DB2 and is associated with the identification information of the communication device assigned to one or more of the plurality of device control units. Get the request content.
 図2を用いて、装置管理部204の処理を詳細に説明する。図2は、収容位置の決定方法を説明する図である。ここで、コンフィグ内容に応じてあらかじめ用意されたシナリオが、装置管理DB203に記憶されているものとする。シナリオは、要求内容によって示される、通信サービスの種類、ユーザ数、通信量等に応じて用意されているものとする。 The processing of the device management unit 204 will be described in detail with reference to FIG. FIG. 2 is a diagram illustrating a method of determining a storage position. Here, it is assumed that the scenario prepared in advance according to the config contents is stored in the device management DB 203. The scenario shall be prepared according to the type of communication service, the number of users, the amount of communication, etc. indicated by the content of the request.
 まず、装置管理部204は、コンフィグ投入要求管理DB202から、要求内容を取得する(2-1)。そして、装置管理部204は、要求内容に応じたシナリオを選択する(2-2)。さらに、装置管理部204は、各通信装置の空きリソースを確認し、収容位置を決定する(2-3)。ここで、収容位置は、コンフィグの投入先の通信装置を意味する。このように、装置管理部204は、あらかじめ用意された要求内容に応じたシナリオに従ってコンフィグ投入を実行する通信装置を決定する。 First, the device management unit 204 acquires the request content from the config input request management DB 202 (2-1). Then, the device management unit 204 selects a scenario according to the content of the request (2-2). Further, the device management unit 204 confirms the free resources of each communication device and determines the accommodation position (2-3). Here, the accommodation position means the communication device to which the config is input. In this way, the device management unit 204 determines the communication device for executing the config input according to the scenario corresponding to the request content prepared in advance.
 図3を用いて、装置制御部210の処理を詳細に説明する。図3は、コンフィグの投入方法を説明する図である。装置制御部210は、あらかじめ用意されたコンフィグ投入のためのコマンドのテンプレートに含まれる所定のパラメータを要求内容及び識別情報に基づき置換して得られるコンマンドを実行する。 The processing of the device control unit 210 will be described in detail with reference to FIG. FIG. 3 is a diagram illustrating a method of inputting a config. The device control unit 210 executes a command obtained by substituting a predetermined parameter included in a template of a command for inputting a config prepared in advance based on a request content and identification information.
 ここで、テンプレートを作成するためのテンプレートファイルが装置管理DB203に記憶されているものとする。装置制御部210は、通信装置の機種や投入要求の内容毎に、テンプレートファイルを用意し、テンプレートファイル内の可変パラメータを置換して、装置に投入するコマンドリストの生成を行う。ここで、パラメータは、ユーザごとに可変の項目であり、例えば、アドレス、ユーザの識別子、通信帯域、料金等である。また、コマンドテンプレートファイルは、コンフィグ投入がサービスの開通、変更、解約のいずれであるか、及びユーザの所属する組織(A社、B社等)ごとに異なっていてもよい。 Here, it is assumed that the template file for creating the template is stored in the device management DB 203. The device control unit 210 prepares a template file for each model of the communication device and the content of the input request, replaces the variable parameters in the template file, and generates a command list to be input to the device. Here, the parameter is a variable item for each user, and is, for example, an address, a user identifier, a communication band, a charge, and the like. Further, the command template file may be different depending on whether the input of the config is opening, changing, or canceling the service, and the organization to which the user belongs (company A, company B, etc.).
 図3に示すように、まず装置制御部210は、コンフィグのテンプレートを選択する(5-1)。次に、装置制御部210は、コマンドリストを作成する(5-2)。そして、装置制御部210は、作成したコマンドを実行し、コンフィグの投入を行う(5-3)。 As shown in FIG. 3, the device control unit 210 first selects a config template (5-1). Next, the device control unit 210 creates a command list (5-2). Then, the device control unit 210 executes the created command and inputs the config (5-3).
 図4及び図5を用いて、リソースコントローラ205の処理を説明する。リソースコントローラ205は、装置制御部210、装置制御部220、装置制御部230、を含む各機能部の動作状況を監視し、状況に応じて各機能部の動作を制御する。リソースコントローラ205は、各機能部に割り当てられるリソース、又はタスクの優先度等を調整する。リソースコントローラ205は、調整部の一例である。 The processing of the resource controller 205 will be described with reference to FIGS. 4 and 5. The resource controller 205 monitors the operation status of each functional unit including the device control unit 210, the device control unit 220, and the device control unit 230, and controls the operation of each functional unit according to the status. The resource controller 205 adjusts the resources assigned to each functional unit, the priority of the task, and the like. The resource controller 205 is an example of an adjustment unit.
 図4は、リソースの制御方法を説明する図である。リソースコントローラ205は、一定時間ごとに受信した投入要求数を監視し、その数に応じた装置制御部のリソース割り当てや、定期監視におけるコンフィグ投入要求管理DB202の確認頻度の変更を行うことで、投入要求の滞留を防ぐことができる。 FIG. 4 is a diagram illustrating a resource control method. The resource controller 205 monitors the number of input requests received at regular intervals, allocates resources in the device control unit according to the number, and changes the confirmation frequency of the config input request management DB 202 in periodic monitoring. It is possible to prevent the request from staying.
 図4は、リソースの制御方法を説明する図である。図4に示すように、まず、リソースコントローラ205は、コンフィグ投入要求管理DB202を参照し、処理待ちの投入要求数を確認する(7)。そして、リソースコントローラ205は、投入要求数に応じたスケールアップ、コンピュートリソースの割り当て、DB確認頻度変更を行う(8)。 FIG. 4 is a diagram illustrating a resource control method. As shown in FIG. 4, first, the resource controller 205 refers to the config input request management DB 202 and confirms the number of input requests waiting to be processed (7). Then, the resource controller 205 scales up according to the number of input requests, allocates compute resources, and changes the DB confirmation frequency (8).
 例えば、通信装置211、通信装置212、通信装置213に対する大量のコンフィグ投入要求がコンフィグ投入要求管理DB202において処理待ちの状態にある場合、装置制御部210のリソースが足りなくなることが考えられる。このような場合、リソースコントローラ205は、装置制御部210aを臨時増設し、増設した装置制御部210aに通信装置211、通信装置212、通信装置213を割り当てる。なお、リソースコントローラ205は、所定のサーバ上に仮想マシンを自動生成することにより増設を行ってもよい。また、リソースコントローラ205は、複数の装置制御部のうち、確認頻度の加速が必要な装置制御部のみ(8)の制御を行うようにしてもよい。 For example, when a large number of config input requests for the communication device 211, the communication device 212, and the communication device 213 are waiting for processing in the config input request management DB 202, it is conceivable that the resources of the device control unit 210 will be insufficient. In such a case, the resource controller 205 temporarily expands the device control unit 210a, and allocates the communication device 211, the communication device 212, and the communication device 213 to the added device control unit 210a. The resource controller 205 may be expanded by automatically generating a virtual machine on a predetermined server. Further, the resource controller 205 may control only the device control unit (8) that needs to accelerate the confirmation frequency among the plurality of device control units.
 このように、リソースコントローラ205は、コンフィグ投入要求管理DB202に記憶された未処理の要求内容の数に基づき、装置制御部210に割り当てるリソース及び装置制御部210によるコンフィグ投入要求管理DB202の監視頻度を調整する。これにより、リソースコントローラ205は、装置制御部の投入要求管理DB202へのアクセス頻度が高すぎて投入要求管理DB202のアクセスリソースが枯渇するのを防ぐことができる。 In this way, the resource controller 205 determines the resources allocated to the device control unit 210 and the monitoring frequency of the config input request management DB 202 by the device control unit 210 based on the number of unprocessed request contents stored in the config input request management DB 202. adjust. As a result, the resource controller 205 can prevent the access resource of the input request management DB 202 from being exhausted because the access frequency to the input request management DB 202 of the device control unit is too high.
 図5は、優先度の制御方法を説明する図である。図5のように、リソースコントローラ205は、コンフィグ投入要求管理DB202に記憶された未処理の要求内容のうち、滞留時間が一定時間以上である要求内容に基づくコンフィグ投入を優先して装置制御部210に処理させることができる。まず、リソースコントローラ205は、滞留中の投入要求(一定時間以上処理されていない)があるか確認する(9)。そして、リソースコントローラ205は、滞留中の投入要求の優先度を高く設定する(10)。これにより、コンフィグ投入要求の滞留が解消される。 FIG. 5 is a diagram illustrating a priority control method. As shown in FIG. 5, the resource controller 205 gives priority to the config input based on the request content whose residence time is a certain time or more among the unprocessed request contents stored in the config input request management DB 202, and the device control unit 210. Can be processed. First, the resource controller 205 confirms whether there is an input request (which has not been processed for a certain period of time or longer) during the stagnation (9). Then, the resource controller 205 sets the priority of the input request during the stagnation high (10). As a result, the stagnation of the config input request is eliminated.
 図6は、第1の実施形態の効果を説明する図である。管理システム20は、機能分散により各機能部の特性に応じた適切な拡張を実施可能にすする。例えば、装置制御部はスケールアウトによる拡張が可能であり、その他の機能部はスケールアップによる拡張が可能である。また、管理システム20では、収容位置決定のシナリオ化、コンフィグ投入のテンプレート化により、新規サービス追加や装置更改等に伴う改造容易性が担保される。 FIG. 6 is a diagram illustrating the effect of the first embodiment. The management system 20 makes it possible to carry out appropriate expansion according to the characteristics of each functional unit by distributing the functions. For example, the device control unit can be expanded by scaling out, and the other functional units can be expanded by scaling up. Further, in the management system 20, the easiness of remodeling due to the addition of a new service, the renewal of the device, etc. is guaranteed by creating a scenario for determining the accommodation position and creating a template for inputting the config.
[第1の実施形態の処理]
 図7は、第1の実施形態の管理システムの処理の流れを示すシーケンス図である。まず、図7に示すように、上位システム対応部201は、上位システム10からコンフィグ投入要求を受け取る(ステップS101)。次に、上位システム対応部201は、受け取ったコンフィグ投入要求をコンフィグ投入要求管理DB202に書き込む(ステップS102)。
[Processing of the first embodiment]
FIG. 7 is a sequence diagram showing a processing flow of the management system of the first embodiment. First, as shown in FIG. 7, the host system corresponding unit 201 receives a config input request from the host system 10 (step S101). Next, the host system corresponding unit 201 writes the received config input request to the config input request management DB 202 (step S102).
 例えば、コンフィグ投入要求管理DB202には、202aに示すようなレコードが書き込まれる。このとき、コンフィグ投入要求の状態は「受付済」である。上位システム対応部201は、上位システム10に対し受付応答を行う(ステップS103)。 For example, a record as shown in 202a is written in the config input request management DB 202. At this time, the status of the config input request is "accepted". The host system correspondence unit 201 makes a reception response to the host system 10 (step S103).
 コンフィグ投入要求管理DB202の実行機能部という項目には、次にコンフィグ投入要求に対して処理を行う機能部(処理の実行中又は実行待ちの機能部)を特定する情報が保持される。各機能部は、当該実行機能部の項目に保持されている情報を基に、コンフィグ投入要求管理DB202から処理すべきコンフィグ投入要求を取得する。202aの例では、次にコンフィグ投入要求に対して処理を行う機能部が「装置管理部」であることが示されている。この場合、202aに示されるコンフィグ投入要求は、装置管理部によって取得されるが、装置制御部及び上位システム対応部によっては取得されない。 The item called the execution function unit of the config input request management DB 202 holds information that identifies the function unit (the function unit that is executing or is waiting to be executed) that processes the next config input request. Each function unit acquires a config input request to be processed from the config input request management DB 202 based on the information held in the item of the execution function unit. In the example of 202a, it is shown that the functional unit that next processes the config input request is the "device management unit". In this case, the config input request shown in 202a is acquired by the device management unit, but is not acquired by the device control unit and the host system corresponding unit.
 装置管理部204は、定期的にコンフィグ投入要求管理DB202から収用位置未決定の要求を取得を試みる(ステップS104、S105)。ここで、装置管理部204は、収用位置未決定の要求が取得できた場合(該当ありの場合)、収容位置決定のためのシナリオを選択する(ステップS106)。 The device management unit 204 periodically attempts to acquire a request for which the expropriation position has not been determined from the config input request management DB 202 (steps S104 and S105). Here, the device management unit 204 selects a scenario for determining the accommodation position when the request for determining the acquisition position can be acquired (if applicable) (step S106).
 また、装置管理部204は、該当ユーザのコンフィグ投入における消費リソースを推定する(ステップS107)。さらに、装置管理部204は、各通信装置の残りリソースを確認する(ステップS108)。このとき、装置管理部204は、確認内容によっては各通信装置と通信し情報を収集する。そして、装置管理部204は、シナリオに従って収容装置を決定する(ステップS109)。ここで、装置管理部204は、決定した収容位置をコンフィグ投入要求管理DB202に書き込む(ステップS110)。 Further, the device management unit 204 estimates the resource consumption in the configuration input of the corresponding user (step S107). Further, the device management unit 204 confirms the remaining resources of each communication device (step S108). At this time, the device management unit 204 communicates with each communication device and collects information depending on the confirmation content. Then, the device management unit 204 determines the accommodating device according to the scenario (step S109). Here, the device management unit 204 writes the determined accommodation position in the config input request management DB 202 (step S110).
 このとき、例えば202bに示すように、コンフィグ投入要求管理DB202には収容位置「#1-1」が書き込まれ、状態は「位置決定済み」に更新される。なお、「#1-1」は、通信装置211を識別するための識別情報である。また、ユーザID、利用サービス、要求種別等の項目が要求内容に相当する。また、202bの例では、次にコンフィグ投入要求に対して処理を行う機能部が「装置制御部」であることが示されている。 At this time, as shown in 202b, for example, the accommodation position "# 1-1" is written in the config input request management DB 202, and the state is updated to "position determined". Note that "# 1-1" is identification information for identifying the communication device 211. In addition, items such as user ID, service used, request type, etc. correspond to the request contents. Further, in the example of 202b, it is shown that the functional unit that next processes the config input request is the “device control unit”.
 装置制御部210は、コンフィグ投入要求管理DB202から、収用位置が配下の通信装置である要求を取得する(ステップS111)。ここで、配下の通信装置とは、各装置制御部に割り当てられた通信装置を意味する。例えば、通信装置211、通信装置212及び通信装置213は、装置制御部210の配下の通信装置である。 The device control unit 210 acquires a request whose expropriation position is a subordinate communication device from the config input request management DB 202 (step S111). Here, the subordinate communication device means a communication device assigned to each device control unit. For example, the communication device 211, the communication device 212, and the communication device 213 are communication devices under the device control unit 210.
 装置制御部210は、要求内容に応じたコマンドテンプレートを選択する(ステップS112)。また、装置制御部210は、選択したコマンドテンプレートを基にコマンドリストを生成する(ステップS113)。そして、装置制御部210は、配下の通信装置211に対しコマンドを実行し、コンフィグ設定を行う(ステップS114)。 The device control unit 210 selects a command template according to the request content (step S112). Further, the device control unit 210 generates a command list based on the selected command template (step S113). Then, the device control unit 210 executes a command to the subordinate communication device 211 to set the configuration (step S114).
 ここで、装置制御部210は、コンフィグ投入要求管理DB202に設定完了の書き込みを行う(ステップS115)。このとき、例えば202cに示すように、コンフィグ投入要求管理DB202の状態は「設定完了済」に更新される。また、202cの例では、次にコンフィグ投入要求に対して処理を行う機能部が「上位システム対応部」であることが示されている。 Here, the device control unit 210 writes the setting completion to the config input request management DB 202 (step S115). At this time, for example, as shown in 202c, the status of the config input request management DB 202 is updated to "setting completed". Further, in the example of 202c, it is shown that the functional unit that next processes the config input request is the "upper system corresponding unit".
 上位システム対応部201は、コンフィグ投入要求管理DB202に設定完了要求の確認を行う(ステップS116)。具体的には、上位システム対応部201は、コンフィグ投入要求管理DB202の状態が「設定完了済」であることを確認する。そして、上位システム対応部201は、上位システム10に対し設定完了を通知する(ステップS117)。 The upper system corresponding unit 201 confirms the setting completion request in the config input request management DB 202 (step S116). Specifically, the host system corresponding unit 201 confirms that the status of the config input request management DB 202 is "setting completed". Then, the host system corresponding unit 201 notifies the host system 10 of the completion of the setting (step S117).
[第1の実施形態の効果]
 これまで説明してきたように、コンフィグ投入要求管理DB202は、ネットワークを利用するユーザを収容する複数の通信装置に対する、コンフィグ投入の要求内容を記憶する。装置管理部204は、要求内容、及び、複数の通信装置のリソースの空き状況を基に、複数の通信装置の中からコンフィグ投入を実行する通信装置を決定し、当該決定した通信装置を識別するための情報を要求内容に対応付けてコンフィグ投入要求管理DB202に格納する。装置制御部210は、要求内容に対応付けられた識別情報によって識別される通信装置に対し、要求内容に基づくコンフィグ投入を実行する。
[Effect of the first embodiment]
As described above, the config input request management DB 202 stores the contents of the config input request for the plurality of communication devices accommodating the users who use the network. The device management unit 204 determines a communication device to execute config input from a plurality of communication devices based on the request contents and the availability of resources of the plurality of communication devices, and identifies the determined communication device. The information for this is stored in the config input request management DB 202 in association with the request contents. The device control unit 210 executes config input based on the request content to the communication device identified by the identification information associated with the request content.
 このように、管理システム20は、処理単位ごとに機能部を分割し、各機能部が自律的にコンフィグ投入要求管理DB202から情報を取得し、各投入要求のステータスに応じた処理を実行し、処理結果をコンフィグ投入要求管理DB202に記録していく。 In this way, the management system 20 divides the functional unit into each processing unit, and each functional unit autonomously acquires information from the config input request management DB 202 and executes processing according to the status of each input request. The processing result is recorded in the config input request management DB 202.
 そのため、管理システム20では、全体の処理を各機能部で細かく分けることで、処理ごとに適切な性能拡張が可能であり、いずれかの機能部が故障してもその他の部は継続して作業を継続できる。また故障した機能部の処理で実施していた処理についても、復旧後あるいは冗長系の機能部からDB状態を読み直すことで低コストで直前の状態から再開できる。また、処理フローの途中で故障が発生しても、容易に他の同一機能部や冗長系が処理を引き継ぐことが可能である。その結果、本実施形態によれば、通信サービスのユーザを管理するシステムにおける冗長性と拡張性が担保される。 Therefore, in the management system 20, by subdividing the entire processing into each functional part, it is possible to appropriately expand the performance for each processing, and even if one of the functional parts fails, the other parts continue to work. Can be continued. In addition, the processing that was performed in the processing of the failed functional part can be restarted from the previous state at low cost by re-reading the DB state after recovery or from the redundant functional part. Further, even if a failure occurs in the middle of the processing flow, another same functional unit or a redundant system can easily take over the processing. As a result, according to the present embodiment, redundancy and expandability in the system for managing the users of the communication service are guaranteed.
 また、管理システム20では、各機能部が次の機能部の処理を指示する方式に比べ、各部の連携動作を規定する必要がなく、開発や機能部の改造が容易になる。具体的には、通信装置の新機種導入やOS更新、新規サービス追加等による通信装置へのコンフィグ投入のためのIF更新、収容位置決定シナリオの変更・追加等、一部の処理での改造が容易に想定される。このような場合に、管理システム20では、一部の処理の改造が他の処理に与える影響を最小化できる。 Further, in the management system 20, it is not necessary to specify the cooperative operation of each part as compared with the method in which each functional part instructs the processing of the next functional part, and the development and the modification of the functional part become easy. Specifically, some processing such as introduction of a new model of communication device, OS update, IF update for inputting config to communication device by adding new service, change / addition of accommodation position determination scenario, etc. Easily assumed. In such a case, the management system 20 can minimize the influence of the modification of some processes on other processes.
 さらに、管理システム20によれば、収容位置決定シナリオの追加・変更内容によっては外部DBやシステムから追加情報の参照や外部シナリオの読み込みを行ったり、上位システムからの要求内容に特殊な指示(要求の優先度付け、収容位置や収容位置決定シナリオの指定、コンフィグコマンド指定、等)を行う等、複雑な改造にも容易に対応できる。 Further, according to the management system 20, depending on the addition / change contents of the accommodation position determination scenario, additional information can be referred from the external DB or the system, the external scenario can be read, or special instructions (requests) can be given to the request contents from the host system. It is possible to easily deal with complicated modifications such as prioritizing, specifying the accommodation position and the accommodation position determination scenario, specifying the config command, etc.).
 装置管理部204は、コンフィグ投入要求管理DB202を定期的に監視し、要求内容を取得する。複数の装置制御部のそれぞれは、コンフィグ投入要求管理DB202を定期的に監視し、複数の装置制御部のうちの1つ又は複数に割り当てられた通信装置の識別情報に対応付けられた要求内容を取得する。これにより、各機能部は、共有するコンフィグ投入要求管理DB202を監視すれば、互いに通知をやり取りする必要はなく、互いに独立して動作することができる。 The device management unit 204 periodically monitors the config input request management DB 202 and acquires the request contents. Each of the plurality of device control units periodically monitors the config input request management DB 202, and the request contents associated with the identification information of the communication device assigned to one or more of the plurality of device control units. get. As a result, if each functional unit monitors the shared config input request management DB 202, it is not necessary to exchange notifications with each other, and each functional unit can operate independently of each other.
 リソースコントローラ205は、コンフィグ投入要求管理DB202に記憶された未処理の要求内容の数に基づき、装置制御部210に割り当てるリソース及び装置制御部210によるコンフィグ投入要求管理DB202の監視頻度を調整する。これにより、監視頻度を抑えることができるため、ピーク時であっても管理システム20全体のリソース量を抑えることができる。 The resource controller 205 adjusts the resources allocated to the device control unit 210 and the monitoring frequency of the config input request management DB 202 by the device control unit 210 based on the number of unprocessed request contents stored in the config input request management DB 202. As a result, the monitoring frequency can be suppressed, so that the amount of resources of the entire management system 20 can be suppressed even during peak hours.
 リソースコントローラ205は、コンフィグ投入要求管理DB202に記憶された未処理の要求内容のうち、滞留時間が一定時間以上である要求内容に基づくコンフィグ投入を優先して装置制御部210に処理させる。これにより、コンフィグ投入要求の滞留を防ぐことができる。 The resource controller 205 causes the device control unit 210 to preferentially process the config input based on the request content whose residence time is a certain time or more among the unprocessed request contents stored in the config input request management DB 202. This makes it possible to prevent the config input request from staying.
 装置管理部204は、あらかじめ用意された要求内容に応じたシナリオに従ってコンフィグ投入を実行する通信装置を決定する。装置制御部210は、あらかじめ用意されたコンフィグ投入のためのコマンドのテンプレートに含まれる所定のパラメータを要求内容及び識別情報に基づき置換して得られるコンマンドを実行する。このように、管理システム20では、シナリオ化やテンプレート化により処理を効率化することができる。 The device management unit 204 determines the communication device for executing the config input according to the scenario according to the request content prepared in advance. The device control unit 210 executes a command obtained by substituting a predetermined parameter included in a template of a command for inputting a config prepared in advance based on a request content and identification information. In this way, in the management system 20, processing can be streamlined by creating scenarios and templates.
[システム構成等]
 また、図示した各装置の各構成要素は機能概念的なものであり、必ずしも物理的に図示のように構成されていることを要しない。すなわち、各装置の分散及び統合の具体的形態は図示のものに限られず、その全部又は一部を、各種の負荷や使用状況等に応じて、任意の単位で機能的又は物理的に分散又は統合して構成することができる。さらに、各装置にて行われる各処理機能は、その全部又は任意の一部が、CPU及び当該CPUにて解析実行されるプログラムにて実現され、あるいは、ワイヤードロジックによるハードウェアとして実現され得る。
[System configuration, etc.]
Further, each component of each of the illustrated devices is a functional concept, and does not necessarily have to be physically configured as shown in the figure. That is, the specific form of distribution and integration of each device is not limited to the one shown in the figure, and all or part of them may be functionally or physically dispersed or physically distributed in arbitrary units according to various loads and usage conditions. Can be integrated and configured. Further, each processing function performed by each device may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware by wired logic.
 また、本実施形態において説明した各処理のうち、自動的に行われるものとして説明した処理の全部又は一部を手動的に行うこともでき、あるいは、手動的に行われるものとして説明した処理の全部又は一部を公知の方法で自動的に行うこともできる。この他、上記文書中や図面中で示した処理手順、制御手順、具体的名称、各種のデータやパラメータを含む情報については、特記する場合を除いて任意に変更することができる。 Further, among the processes described in the present embodiment, all or part of the processes described as being automatically performed can be manually performed, or the processes described as being manually performed can be performed. All or part of it can be done automatically by a known method. In addition, the processing procedure, control procedure, specific name, and information including various data and parameters shown in the above document and drawings can be arbitrarily changed unless otherwise specified.
[プログラム]
 一実施形態として、管理システム20は、パッケージソフトウェアやオンラインソフトウェアとして上記の管理処理を実行する管理プログラムを所望のコンピュータにインストールさせることによって実装できる。例えば、上記の管理プログラムを情報処理装置に実行させることにより、情報処理装置を管理システム20として機能させることができる。ここで言う情報処理装置には、デスクトップ型又はノート型のパーソナルコンピュータが含まれる。また、その他にも、情報処理装置にはスマートフォン、携帯電話機やPHS(Personal Handyphone System)等の移動体通信端末、さらには、PDA(Personal Digital Assistant)等のスレート端末等がその範疇に含まれる。
[program]
As one embodiment, the management system 20 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, by causing the information processing apparatus to execute the above management program, the information processing apparatus can function as the management system 20. The information processing device referred to here includes a desktop type or notebook type personal computer. In addition, information processing devices include smartphones, mobile communication terminals such as mobile phones and PHS (Personal Handyphone System), and slate terminals such as PDAs (Personal Digital Assistants).
 また、管理システム20は、ユーザが使用する端末装置をクライアントとし、当該クライアントに上記の管理処理に関するサービスを提供する管理サーバ装置として実装することもできる。例えば、管理サーバ装置は、コンフィグ投入要求を入力とし、コンフィグ投入を行う管理サービスを提供するサーバ装置として実装される。この場合、管理サーバ装置は、Webサーバとして実装することとしてもよいし、アウトソーシングによって上記の管理処理に関するサービスを提供するクラウドとして実装することとしてもかまわない。 Further, the management system 20 can be implemented as a management server device in which the terminal device used by the user is a client and the service related to the above management process is provided to the client. For example, the management server device is implemented as a server device that receives a config input request as an input and provides a management service for inputting a config. In this case, the management server device may be implemented as a Web server, or may be implemented as a cloud that provides services related to the above management processing by outsourcing.
 図9は、管理プログラムを実行するコンピュータの一例を示す図である。コンピュータ1000は、例えば、メモリ1010、CPU1020を有する。また、コンピュータ1000は、ハードディスクドライブインタフェース1030、ディスクドライブインタフェース1040、シリアルポートインタフェース1050、ビデオアダプタ1060、ネットワークインタフェース1070を有する。これらの各部は、バス1080によって接続される。 FIG. 9 is a diagram showing an example of a computer that executes a management program. The computer 1000 has, for example, a memory 1010 and a CPU 1020. The computer 1000 also has 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. Each of these parts is connected by a bus 1080.
 メモリ1010は、ROM(Read Only Memory)1011及びRAM1012を含む。ROM1011は、例えば、BIOS(BASIC Input Output System)等のブートプログラムを記憶する。ハードディスクドライブインタフェース1030は、ハードディスクドライブ1090に接続される。ディスクドライブインタフェース1040は、ディスクドライブ1100に接続される。例えば磁気ディスクや光ディスク等の着脱可能な記憶媒体が、ディスクドライブ1100に挿入される。シリアルポートインタフェース1050は、例えばマウス1110、キーボード1120に接続される。ビデオアダプタ1060は、例えばディスプレイ1130に接続される。 The memory 1010 includes a ROM (Read Only Memory) 1011 and a RAM 1012. The ROM 1011 stores, for example, a boot program such as a BIOS (BASIC Input Output System). The hard disk drive interface 1030 is connected to the hard disk drive 1090. The disk drive interface 1040 is connected to the disk drive 1100. For example, a removable storage medium such as a magnetic disk or an optical disk is inserted into the disk drive 1100. The serial port interface 1050 is connected to, for example, a mouse 1110 and a keyboard 1120. The video adapter 1060 is connected to, for example, the display 1130.
 ハードディスクドライブ1090は、例えば、OS1091、アプリケーションプログラム1092、プログラムモジュール1093、プログラムデータ1094を記憶する。すなわち、管理システム20と同等の機能を持つ管理装置の各処理を規定するプログラムは、コンピュータにより実行可能なコードが記述されたプログラムモジュール1093として実装される。プログラムモジュール1093は、例えばハードディスクドライブ1090に記憶される。例えば、管理装置における機能構成と同様の処理を実行するためのプログラムモジュール1093が、ハードディスクドライブ1090に記憶される。なお、ハードディスクドライブ1090は、SSDにより代替されてもよい。 The hard disk drive 1090 stores, for example, the OS 1091, the application program 1092, the program module 1093, and the program data 1094. That is, the program that defines each process of the management device having the same function as the management system 20 is implemented as the program module 1093 in which the code that can be executed by the computer is described. The program module 1093 is stored in, for example, the hard disk drive 1090. For example, the program module 1093 for executing the same processing as the functional configuration in the management device is stored in the hard disk drive 1090. The hard disk drive 1090 may be replaced by an SSD.
 また、上述した実施形態の処理で用いられる設定データは、プログラムデータ1094として、例えばメモリ1010やハードディスクドライブ1090に記憶される。そして、CPU1020は、メモリ1010やハードディスクドライブ1090に記憶されたプログラムモジュール1093やプログラムデータ1094を必要に応じてRAM1012に読み出して、上述した実施形態の処理を実行する。 Further, the setting data used in the processing of the above-described embodiment is stored as program data 1094 in, for example, a memory 1010 or a hard disk drive 1090. Then, the CPU 1020 reads the program module 1093 and the program data 1094 stored in the memory 1010 and the hard disk drive 1090 into the RAM 1012 as needed, and executes the process of the above-described embodiment.
 なお、プログラムモジュール1093やプログラムデータ1094は、ハードディスクドライブ1090に記憶される場合に限らず、例えば着脱可能な記憶媒体に記憶され、ディスクドライブ1100等を介してCPU1020によって読み出されてもよい。あるいは、プログラムモジュール1093及びプログラムデータ1094は、ネットワーク(LAN(Local Area Network)、WAN(Wide Area Network)等)を介して接続された他のコンピュータに記憶されてもよい。そして、プログラムモジュール1093及びプログラムデータ1094は、他のコンピュータから、ネットワークインタフェース1070を介してCPU1020によって読み出されてもよい。 The program module 1093 and the program data 1094 are not limited to those stored in the hard disk drive 1090, but may be stored in, for example, a removable storage medium and read by the CPU 1020 via the disk drive 1100 or the like. Alternatively, the program module 1093 and the program data 1094 may be stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.). Then, the program module 1093 and the program data 1094 may be read from another computer by the CPU 1020 via the network interface 1070.
 N L2ネットワーク
 10 上位システム
 20 管理システム
 201 上位システム対応部
 202 コンフィグ投入要求管理DB
 203 装置管理DB
 204 装置管理部
 205 リソースコントローラ
 210、220、230 装置制御部
 211、212、213、221、222、223、231、232、233 通信装置
 U11、U12 ユーザ
N L2 network 10 Upper system 20 Management system 201 Upper system correspondence part 202 Config input request management DB
203 Device management DB
204 Device management unit 205 Resource controller 210, 220, 230 Device control unit 211, 212, 213, 211, 222, 223, 231, 232, 233 Communication device U11, U12 User

Claims (8)

  1.  ネットワークを利用するユーザを収容する複数の通信装置に対する、コンフィグ投入の要求内容を記憶する記憶部と、
     前記要求内容、及び、前記複数の通信装置のリソースの空き状況を基に、前記複数の通信装置の中からコンフィグ投入を実行する通信装置を決定し、当該決定した通信装置を識別するための識別情報を前記要求内容に対応付けて前記記憶部に格納する決定部と、
     前記要求内容に対応付けられた前記識別情報によって識別される通信装置に対し、前記要求内容に基づくコンフィグ投入を実行する実行部と、
     を有することを特徴とする管理装置。
    A storage unit that stores the contents of config input requests for multiple communication devices that accommodate users who use the network.
    Identification for identifying the determined communication device by determining the communication device to execute the config input from the plurality of communication devices based on the request contents and the availability of resources of the plurality of communication devices. A determination unit that stores information in the storage unit in association with the request content, and a determination unit.
    An execution unit that executes config input based on the request content to the communication device identified by the identification information associated with the request content, and an execution unit.
    A management device characterized by having.
  2.  前記決定部は、前記記憶部を定期的に監視し、前記要求内容を取得し、
     複数の前記実行部のそれぞれは、前記記憶部を定期的に監視し、複数の前記実行部のうちの1つ又は複数に割り当てられた通信装置の前記識別情報に対応付けられた前記要求内容を取得することを特徴とする請求項1に記載の管理装置。
    The determination unit periodically monitors the storage unit, acquires the request content, and obtains the request content.
    Each of the plurality of execution units periodically monitors the storage unit, and the request content associated with the identification information of the communication device assigned to one or more of the plurality of execution units. The management device according to claim 1, wherein the management device is to be acquired.
  3.  前記記憶部に記憶された未処理の前記要求内容の数に基づき、前記実行部に割り当てるリソース及び前記実行部による前記記憶部の監視頻度を調整する調整部をさらに有することを特徴とする請求項2に記載の管理装置。 The claim is characterized in that it further includes a resource allocated to the execution unit and an adjustment unit for adjusting the monitoring frequency of the storage unit by the execution unit based on the number of unprocessed request contents stored in the storage unit. 2. The management device according to 2.
  4.  前記調整部は、前記記憶部に記憶された未処理の前記要求内容のうち、滞留時間が一定時間以上である要求内容に基づくコンフィグ投入を優先して前記実行部に処理させることを特徴とする請求項3に記載の管理装置。 The adjusting unit is characterized in that, among the unprocessed request contents stored in the storage unit, the execution unit preferentially processes the config input based on the request content having a residence time of a certain time or more. The management device according to claim 3.
  5.  前記決定部は、あらかじめ用意された前記要求内容に応じたシナリオに従ってコンフィグ投入を実行する通信装置を決定し、
     前記実行部は、あらかじめ用意されたコンフィグ投入のためのコマンドのテンプレートに含まれる所定のパラメータを前記要求内容及び前記識別情報に基づき置換して得られるコンマンドを実行することを特徴とする請求項1から3のいずれか1項に記載の管理装置。
    The determination unit determines a communication device that executes config input according to a scenario prepared in advance according to the request content.
    The execution unit is characterized in that it executes a command obtained by substituting a predetermined parameter included in a template of a command for inputting a config prepared in advance based on the request content and the identification information. The management device according to any one of 3 to 3.
  6.  ネットワークを利用するユーザを収容する複数の通信装置に対する、コンフィグ投入の要求内容を記憶する記憶部を有する管理装置によって実行される管理方法であって、
     前記要求内容、及び、前記複数の通信装置のリソースの空き状況を基に、前記複数の通信装置の中からコンフィグ投入を実行する通信装置を決定し、当該決定した通信装置を識別するための識別情報を前記要求内容に対応付けて前記記憶部に格納する決定工程と、
     前記要求内容に対応付けられた前記識別情報によって識別される通信装置に対し、前記要求内容に基づくコンフィグ投入を実行する実行工程と、
     を含むことを特徴とする管理方法。
    It is a management method executed by a management device having a storage unit for storing the contents of a config input request for a plurality of communication devices accommodating users who use the network.
    Identification for identifying the determined communication device by determining the communication device to execute the config input from the plurality of communication devices based on the request contents and the availability of resources of the plurality of communication devices. A determination step of associating information with the request content and storing it in the storage unit, and
    An execution step of executing a config input based on the request content for a communication device identified by the identification information associated with the request content, and an execution step.
    A management method characterized by including.
  7.  コンピュータを、請求項1から4のいずれか1項に記載の管理装置として機能させるための管理プログラム。 A management program for making a computer function as the management device according to any one of claims 1 to 4.
  8.  ネットワークを利用するユーザを収容する複数の通信装置に対する、コンフィグ投入の要求内容を記憶する記憶装置と、
     前記要求内容、及び、前記複数の通信装置のリソースの空き状況を基に、前記複数の通信装置の中からコンフィグ投入を実行する通信装置を決定し、当該決定した通信装置を識別するための識別情報を前記要求内容に対応付けて前記記憶装置に格納する第1の装置と、
     前記要求内容に対応付けられた前記識別情報によって識別される通信装置に対し、前記要求内容に基づくコンフィグ投入を実行する第2の装置と、
     を有することを特徴とする管理システム。
    A storage device that stores the contents of the config input request for multiple communication devices that accommodate users who use the network, and a storage device that stores the contents of the config input request.
    Based on the request contents and the availability of resources of the plurality of communication devices, the communication device for executing the config input is determined from the plurality of communication devices, and the identification for identifying the determined communication device is performed. A first device that stores information in the storage device in association with the request content, and
    A second device that executes config input based on the request content to the communication device identified by the identification information associated with the request content, and
    A management system characterized by having.
PCT/JP2020/026106 2020-07-02 2020-07-02 Management device, management method, management program, and management system WO2022003926A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2022532974A JP7439928B2 (en) 2020-07-02 2020-07-02 Management device, management method, management program, and management system
PCT/JP2020/026106 WO2022003926A1 (en) 2020-07-02 2020-07-02 Management device, management method, management program, and management system

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2020/026106 WO2022003926A1 (en) 2020-07-02 2020-07-02 Management device, management method, management program, and management system

Publications (1)

Publication Number Publication Date
WO2022003926A1 true WO2022003926A1 (en) 2022-01-06

Family

ID=79315853

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2020/026106 WO2022003926A1 (en) 2020-07-02 2020-07-02 Management device, management method, management program, and management system

Country Status (2)

Country Link
JP (1) JP7439928B2 (en)
WO (1) WO2022003926A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023157204A1 (en) * 2022-02-17 2023-08-24 日本電信電話株式会社 Configuration inputting device, configuration inputting method and configuration inputting program
WO2024042590A1 (en) * 2022-08-22 2024-02-29 日本電信電話株式会社 Configuration input device, configuration input method and configuration input program

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015037267A (en) * 2013-08-14 2015-02-23 日本電信電話株式会社 Network apparatus setting system and network apparatus setting method
WO2020040133A1 (en) * 2018-08-23 2020-02-27 日本電信電話株式会社 Network management device and network management method

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015037267A (en) * 2013-08-14 2015-02-23 日本電信電話株式会社 Network apparatus setting system and network apparatus setting method
WO2020040133A1 (en) * 2018-08-23 2020-02-27 日本電信電話株式会社 Network management device and network management method

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023157204A1 (en) * 2022-02-17 2023-08-24 日本電信電話株式会社 Configuration inputting device, configuration inputting method and configuration inputting program
WO2024042590A1 (en) * 2022-08-22 2024-02-29 日本電信電話株式会社 Configuration input device, configuration input method and configuration input program

Also Published As

Publication number Publication date
JPWO2022003926A1 (en) 2022-01-06
JP7439928B2 (en) 2024-02-28

Similar Documents

Publication Publication Date Title
CN111782232A (en) Cluster deployment method and device, terminal equipment and storage medium
CN108062254B (en) Job processing method, device, storage medium and equipment
JP7161262B2 (en) A system that optimizes the distribution of automated processes
US9396026B2 (en) Allocating a task to a computer based on determined resources
US20070244999A1 (en) Method, apparatus, and computer product for updating software
Hategan et al. Coasters: uniform resource provisioning and access for clouds and grids
CN103620578B (en) Local cloud computing via network segmentation
US20110239216A1 (en) Service providing system, a virtual machine server, a service providing method, and a program thereof
US20140380411A1 (en) Techniques for workload spawning
CN103294765A (en) Policy-based approach and system for provisioning and transforming virtual appliances
JP2005056391A (en) Method and system for balancing workload of computing environment
WO2022003926A1 (en) Management device, management method, management program, and management system
US20200110631A1 (en) Virtual machine deployment method and omm virtual machine
JP2018527668A (en) Method and system for limiting data traffic
WO2019083579A1 (en) MANAGING MULTI-SINGLE-TENANT SaaS SERVICES
KR20150085309A (en) The Method and System of Providing Server Virtual Machine for Real-time Virtual Desktop Service, and Server device supporting the same
CN113495732A (en) Server deployment method, device, equipment and readable storage medium
CN111970354A (en) Application management method in edge calculation and related device
US20110179171A1 (en) Unidirectional Resource And Type Dependencies In Oracle Clusterware
JP6668658B2 (en) Job management method, job management device, and program
US20210373538A1 (en) Control Apparatus
WO2022044341A1 (en) Management device, management method, management program and management system
US20150212834A1 (en) Interoperation method of newtork device performed by computing device including cloud operating system in could environment
JP6254963B2 (en) Distributed processing system and distributed processing method
WO2022176033A1 (en) Management device, management method, and management program

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 2022532974

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20943045

Country of ref document: EP

Kind code of ref document: A1