Generation device, generation method, and generation program

Abstract

A generation device (30) according to an embodiment of the present invention comprises a reception unit (31) and a synthesis unit (32). The reception unit (31) receives input of an input file in which is defined information that is for executing a configuration input for a communication device that accommodates a user using a network, and that differs depending on the model of the communication device. The synthesis unit (32) synthesizes the input file and a common-definition file in which is defined information that is for executing a configuration input for a communication device, and that is common among models of the communication device.

Description

[Technical Field]

[0001] The present invention relates to a generating device, a generating method, and a generating program. [Background technology]

[0002] Conventionally, communication devices in IP networks perform the control required to provide various services for each user based on configuration information set for each user. In this case, a procedure called configuration input is performed to input the settings required for each user's contracted service into the communication device. Configuration input is sometimes performed by a server called a configuration input server. The communication device is, for example, an edge router (hereinafter referred to as "edge").

[0003] On the other hand, because necessary additions and changes to settings may occur even during operation, it is desirable that the application part of the configuration input server be easy to modify.In response to this, a configuration input server configuration using Ansible, a configuration management tool for automatic configuration of servers, etc., has been proposed (see, for example, Non-Patent Document 1). [Prior art documents] [Non-patent literature]

[0004] [Non-Patent Document 1] Iwahashi et al., “User configuration input to easily modifiable edge routers using Ansible,” Proceedings of the 2021 IEICE General Conference, B-6-67, Mar. 2021. Summary of the Invention [Problem to be solved by the invention]

[0005] However, the conventional method has a problem in that it may not be possible to efficiently obtain data for issuing commands to a communication device.

[0006] For example, the code for executing command input is composed of the desired scenario. To finalize such code, it is necessary to undergo various network verifications by experienced network designers. This can result in a prolonged code development process.

[0007] In addition, after network verification is completed, the development process shifts to software development, which can lead to a sequential development schedule, putting pressure on the overall development schedule. Furthermore, software developers may misinterpret the command instructions provided by experienced network designers, which can lead to bugs.

[0008] As described above, it is difficult to efficiently develop the code for command submission, which reduces the efficiency of the entire command submission procedure. [Means for solving the problem]

[0009] In order to solve the above-mentioned problems and achieve the objective, the generating device is characterized by having a receiving unit that receives input of a first file that defines information for executing configuration input to a communication device that accommodates a user using a network, the first file defining information that differs depending on the model of the communication device, and a synthesis unit that synthesizes the first file with a second file that defines information for executing configuration input to the communication device, the second file defining information common to the model of the communication device. [Effects of the Invention]

[0010] According to the present invention, data for issuing commands to a communication device can be obtained efficiently. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a diagram illustrating an example of the configuration of a management system according to the first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a hierarchical structure for managing templates. [Figure 3] FIG. 3 is a diagram illustrating an example of a hierarchical structure for managing templates. [Figure 4] FIG. 4 is a diagram illustrating the command conversion unit. [Figure 5] FIG. 5 is a diagram illustrating an example of the configuration of a generating device according to the first embodiment. [Figure 6] FIG. 6 is a diagram illustrating an example of the configuration of the command conversion unit according to the first embodiment. [Figure 7] FIG. 7 is a diagram showing an example of an input file. [Figure 8] FIG. 8 is a diagram illustrating an example of branch processing for each branch condition. [Figure 9] FIG. 9 is a sequence diagram showing the flow of processing in the management system. [Figure 10] FIG. 10 is a flowchart showing the flow of processing by the generation device. [Figure 11] FIG. 11 is a flowchart showing the flow of processing by the command conversion unit. [Figure 12] FIG. 12 illustrates an example of a computer that executes a generation program. DETAILED DESCRIPTION OF THE INVENTION

[0012] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] The following describes in detail embodiments of a generating device, a generating method, and a generating program according to the present application, with reference to the accompanying drawings. However, the present invention is not limited to the embodiments described below.

[0013] The generating device, generating method, and generating program also generate command conversion data used in the management system, so the configuration of the management system will also be described.

[0014] [Configuration of the first embodiment] First, the configuration of a management system according to the first embodiment will be described with reference to FIG. 1. FIG. 1 is a diagram showing an example of the configuration of the management system according to the first embodiment. As shown in FIG. 1, the management system 1 includes a management device 10, an edge 20A, an edge 20B, and an edge 20C. An edge is an example of a communication device. Each edge accommodates users who use communication services. Company A, Company B, and Company C are examples of users. The communication device may also be a switch, a router, etc.

[0015] The management device 10 receives a configuration input request from the upper system 2. The configuration input request may be referred to as an SO (service order).

[0016] The functions of the upper system 2 may be realized by an operator. In this case, the operator inputs the contents of a configuration input request into the management system 1. For example, inputting a configuration means making settings for a communication device that accommodates a user, such as when opening, changing, or canceling a service.

[0017] As shown in FIG. 1, the management device 10 includes a host system support unit 11, a configuration input request management DB 12, a decision unit 13, a device control unit 14A, a device control unit 14B, and a device control unit 14C.

[0018] Here, the management device 10 may be realized by a plurality of computers or by a single computer. Each of the configuration input request management DB 12, the determination unit 13, the device control unit 14A, the device control unit 14B, and the device control unit 14C may be realized by a physical machine or a virtual machine.

[0019] First, the host system correspondence unit 11 receives a configuration entry request from the host system 2. The host system correspondence unit 11 registers the received configuration entry request in the configuration entry request management DB 12. As a result, the configuration entry request management DB 12 stores the contents of the configuration entry requests for multiple communication devices that accommodate users who use the network.

[0020] The determination unit 13 performs priority control of the orders (configuration input requests) stored in the configuration input request management DB 12, determines the physical location of the user, and so on.

[0021] The device control unit 14A, the device control unit 14B, and the device control unit 14C perform similar processes. Here, the device control unit 14A will be described as an example.

[0022] The device control unit 14A has a common control unit 141A, an individual control unit 142A, and a command conversion unit 143A.

[0023] The common control unit 141A acquires a request for configuration input to a communication device that accommodates a user who uses the network. For example, the common control unit 141A acquires a request (order) for configuration input from the configuration input request management DB 12, and performs exclusive control on the acquired order.

[0024] Furthermore, the common control unit 141A acquires information about the edge to which the data is to be submitted, which includes the model, version, and use of the edge.

[0025] Furthermore, the common control unit 141A calls the relevant individual control unit 142A based on the scenario information of the order.

[0026] The individual control unit 142A identifies a set of variables required for the command to execute configuration entry based on the content of the request for configuration entry received by the common control unit 141A and the type of communication device, and transmits the identified set of variables to the common control unit 141A. The type of communication device is, for example, an edge model.

[0027] The individual control unit 142A writes the identified variable set into a variable file, and transmits the variable file to the common control unit 141A.

[0028] Here, the common control unit 141A uses the variable file received from the individual control unit 142A as an argument to instruct the command conversion unit 143 to create and execute a command.

[0029] The command conversion section 143A acquires the set of variables specified by the individual control section 142A from the common control section 141A, creates a command based on the acquired set of variables, and executes the created command.

[0030] Here, the command conversion unit 143A holds templates for each type of communication device, version of communication device, and purpose of communication device, and creates commands based on the templates.

[0031] 2 and 3 are diagrams showing an example of a hierarchical structure for managing templates. As shown in Fig. 2 and 3, templates are managed for each model, version, and purpose of a communication device.

[0032] Figure 2 shows that there are templates for the model "Model A", version "1.0", and purpose "for normal users", which correspond to the "SO installation scenario", "maintenance relocation scenario", and "fault relocation scenario".

[0033] Furthermore, the "SO Introduction Scenario" has a "PPPoE service setting function" and an "IPv6 service setting function" as function branches within the scenario. These function branches are set because even within the scenario, whether or not a service is set may change depending on the needs of each user, and the setting order may be taken into consideration depending on the device specifications.

[0034] On the other hand, Fig. 3 shows a template with a model number of "Model A," a version number of "1.0," and a purpose number of "For corporate users." The template in Fig. 2 and the template in Fig. 3 have the same model number and version number, but different purposes.

[0035] The command conversion unit 143A also transmits a log relating to the execution of the command to the common control unit 141A. At this time, the common control unit 141A stores the result of the configuration entry in the configuration entry request management DB 12 based on the log transmitted by the command conversion unit 143A.

[0036] As explained above, the command conversion units (for example, the command conversion unit 143A and the command conversion unit 143B) execute commands to communication devices such as edges according to a scenario.

[0037] On the other hand, there are cases where a new communication device to be configured is added, where the model of the newly added communication device is different from the model of the existing communication device, and where a new scenario for configuring an existing communication device is added.

[0038] 4 is a diagram illustrating the command conversion unit. In the example of FIG. 4, it is assumed that an edge device 20B' to which a configuration is to be input is newly added. However, the model of the edge device 20B' is different from the model of the edge device 20B.

[0039] In this case, it is desirable that data for command conversion for executing a command targeting edge 20B' be quickly added to command conversion unit 143B. The data for command conversion includes a file in which the code of the command itself is written, and a file in which information necessary for executing the command is written.

[0040] A generation device according to an embodiment generates command conversion data for executing commands during configuration input. The command conversion data generated by the generation device may be automatically added to the command conversion unit. Alternatively, the command conversion data generated by the generation device may be added to the command conversion unit by a software developer.

[0041] Fig. 5 is a diagram illustrating an example of the configuration of a generating device according to the first embodiment. As illustrated in Fig. 5, an input file is input to the generating device 30. The generating device 30 outputs command conversion data. For example, the input file is created by a network designer. For example, the command conversion data is used by a software developer.

[0042] The receiving unit 31 receives input of an input file that defines information for executing configuration input for a communication device that accommodates a user who uses the network, and that differs depending on the model of the communication device.

[0043] The input file is a file in which definitions of commands for each model are input according to an input format. The receiving unit 31 is an interface for receiving input of the input file.

[0044] The synthesis unit 32 synthesizes the input file with a common definition file that defines information common to the model of the communication device and is used to input a configuration to the communication device.

[0045] The common definition file is stored in advance in the generating device 30. The input file is an example of a first file. The common definition file is an example of a second file.

[0046] Here, the configuration of the command conversion unit to which the command conversion data is added will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of the configuration of the command conversion unit of the first embodiment. Here, the command conversion unit 143B of the management system 1 will be described as an example.

[0047] As shown in FIG. 6, the command conversion unit 143B has a common processing unit 1431B, a model-specific processing unit 1431B_1, and a model-specific processing unit 1431B_2.

[0048] The per-model processing unit 1431B_1 and the per-model processing unit 1431B_2 correspond to communication devices of different models. For example, the per-model processing unit 1431B_1 is data for inputting a configuration for edge B. Also, for example, the per-model processing unit 1431B_2 is data for inputting a configuration for edge B'. In this way, the command conversion unit has a hierarchical structure divided for each model.

[0049] The model-specific processing unit 1431B_1 and the model-specific processing unit 1431B_2 are generated by the generating device 30.

[0050] Here, the description will be given taking the model-specific processing unit 1431B_1 as an example. The generating device 30 generates a scenario file and a parameter file for the model-specific processing unit 1431B_1 based on the common definition file.

[0051] Furthermore, the generating device 30 generates a command file and an input result check file for the model-specific processing unit 1431B_1 based on the input file.

[0052] A scenario file is a file that abstractly describes a scenario to be executed. For example, the common control unit 141B issues instructions in a format such as "exe model / parameter address change scenario," which specifies the model, parameters, and scenario.

[0053] The model-specific processing unit 1431B_1 instructs the common processing unit 1431 to execute a task based on the scenario file and in accordance with instructions from the common control unit 141B. If the scenario includes multiple tasks, the model-specific processing unit 1431B_1 instructs execution of the tasks as many times as there are tasks.

[0054] The model-specific processing unit 1431B_1 executes commands and checks execution results according to the tasks executed by the common processing unit 1431B. The code of the commands to be executed is written in a command file. The details of the execution result check are written in an input result check file.

[0055] The parameter file is a fixed file for each model, and is allocated when a command is executed.

[0056] 6, the input file includes a command file and an input result check file, and the common definition file includes a file corresponding to the common processing unit 1431B, a scenario file, and a parameter file.

[0057] That is, the receiving unit 31 receives an input of an input file in which a command group that differs depending on the model of the communication device is described. The command group that differs depending on the model of the communication device and that is described in the input file corresponds to a command file.

[0058] It can be said that the command file is called when the common processing section 1431B executes a task, and therefore it can be said that the command file describes the commands that are called when the task is executed.

[0059] The receiving unit 31 also receives an input file that further describes an error detection process for when a command is executed. The error detection process for when a command is executed, which is described in the input file, corresponds to an input result check file.

[0060] The format of the input file will be explained using Figure 7. As shown in Figure 7, the input file is a file in a format (for example, table format, CSV format, XML format, etc.) that consists of item names and values.

[0061] The input file includes items such as "scenario," "command file name," "command," "variable," "response message," "repeated processing," "branching processing," and "update of retained information."

[0062] The item "scenario" stores information for identifying the scenario in which the command is executed, such as the name of the scenario and an ID for identifying the scenario.

[0063] The item "command file name" stores the name of the command file in the command conversion unit.

[0064] The command to be executed is stored in the "command" item. The command is executed using information in the "variable," "response message," "repeated processing," and "branch processing" items, which will be described later.

[0065] The "variable" item stores information indicating variables used in the command. The "response message" item stores a response message when the command is executed successfully.

[0066] The item "repeated processing" stores the content of repeated processing in the command. The item "branch processing" stores the content of branch processing in the command.

[0067] In this way, the receiving unit 31 receives input of an input file that includes variables (item "Variables") used in commands called in the execution of a task, a response message when the command is executed successfully (item "Response Message"), the contents of the repeating process (item "Repeating Process"), the contents of the branching process (item "Branching Process"), and information on parameters that are updated in the execution of the command (item "Update of Retained Information").

[0068] (Scenario: Address change) We will explain the commands included in the "Address Change" scenario in Figure 7. For example, in the "{}" of the command "interface {} in {}", the variables appear in the specified order. Since the variables are specified as "vlan_id_1, vlan_id_2", the first "{}" contains "vlan_id_1" and the second "{}" contains "vlan_id_2".

[0069] Additionally, "{{}}" in a command indicates a repetitive process. For example, the repetitive process of the command "ipv4 address {{}}" is "1_v4_addr_*(1-2)", and the repeated variable is defined as "(numeric value - numeric value)" (e.g., "(1-2)").

[0070] Also, if a command has a repeat section, a number indicating the order in which it appears is added to the beginning of the repeat process, such as "1_v4_addr_*(1-2)". In this case, the two commands "ipv4 address{{}}" and "ipv6 nd suppress" have "1_" at the beginning of their repeat processes, so these two commands make up the repeat section.

[0071] The results of executing the commands included in the scenario "Address Change" are as follows. ipv6 address v6_addr_1 ipv6 address v6_addr_2 ipv4 address v4_addr_1 ipv6 nd suppress ipv4 address v4_addr_2 ipv6 nd suppress

[0072] (Scenario: Policy Registration) The commands included in the scenario "Policy Registration" in Fig. 7 include branching processing. The branching conditions and the contents of the branching processing are shown in Fig. 8. Fig. 8 is a diagram showing an example of branching processing for each branching condition. Note that "var" in Fig. 8 means a variable, and "vars" means a list of variables.

[0073] For example, if the repeat process is "1_" and the branch process is "(up_service_name) != None", this means that the "1_" part is repeated the number of times equal to the number of variables stored as "up_service_name".

[0074] Furthermore, the item "update maintenance information" being "new g_edge_address = command_result" means that after the command is executed, the command result is stored in the variable "g_edge_address" and updated.

[0075] If "* (don't care)" is set in the "Response Message" item, the input result will not be checked. On the other hand, if a value other than "* (don't care)", such as "Success!", is set in the "Response Message" item, the input result will be checked. The "Response Message" item is used to create the input result check file.

[0076] [Processing of the first embodiment] 9 is a sequence diagram showing the processing flow of the management system of the first embodiment. First, as shown in FIG. 9, the host system support unit 11 receives a configuration entry request from the host system 2 (step S101). Next, the host system support unit 11 writes the received configuration entry request into the configuration entry request management DB 12 (step S102).

[0077] The determination unit 13 periodically attempts to acquire requests for which an expropriation location has not been determined from the configuration input request management DB 12 (steps S103 and S104). Here, if the determination unit 13 can acquire a request for which an expropriation location has not been determined (if there is a match), it determines an accommodation location (step S105).

[0078] The determination unit 13 writes the accommodation location in the configuration input request management DB 12 (step S106). The common control unit 141A acquires the request whose accommodation location is a communication device under the control of the device control unit 14A, and performs exclusive control (step S108). The communication device under the control of the device control unit 14A is, for example, the edge 20A.

[0079] Here, the common control unit 141A calls the individual control unit 142A (step S109). The individual control unit 142A checks the status of the communication device (edge ​​20A) (step S110) and creates a variable file (step S111). Then, the individual control unit 142A transmits the created variable file to the common control unit 141A (step S112).

[0080] Based on the variable file, the common control unit 141A requests the command conversion unit 143A to input a command (step S113). The command conversion unit 143A selects a template based on the command input request (step S114).

[0081] The command conversion unit 143A creates a command based on the selected command template (step S115).The command conversion unit 143A then executes the created command on the Edge 20A to input a configuration (step S116).

[0082] Here, the command conversion unit 143A acquires the introduction log from the Edge 20A (step S117), and transmits the acquired introduction log to the common control unit 141A as an introduction result (step S118).

[0083] The common control unit 141A writes the input result to the configuration input request management DB 12 (step S119). The upper system support unit 11 checks the configuration input request management DB 12 for a setting completion request (step S120). Then, the upper system support unit 11 notifies the upper system 2 of the setting completion (step S121).

[0084] 10 is a flowchart showing the flow of processing by the generating device 30. As shown in FIG. 10, first, the generating device 30 receives an input file (step S201).

[0085] Next, the generating device 30 combines the input file and the common definition file (step S202), and then outputs the command conversion data obtained by the combination (step S203).

[0086] The command conversion data generated by the generating device 30 is used by the command conversion unit of the management system 1. Fig. 11 is a flowchart showing the flow of processing by the command conversion unit.

[0087] Here, the command conversion unit 143B will be described as an example. As shown in Fig. 11, first, the command conversion unit 143B starts executing the scenario specified by the common control unit 141B (step S301).

[0088] Next, the command conversion unit 143B executes the task described in the scenario (step S302). The association between the scenario and the task is indicated in a scenario file generated from the common definition file.

[0089] Next, the command conversion unit 143B executes the command according to the command file (step S303). Also, the command conversion unit 143B checks the execution result of the command according to the input result check file (step S304). The command file and the input result check file are generated from the input file.

[0090] Then, the command conversion unit 143B updates the parameters in the parameter file as necessary (step S305).

[0091] [Advantages of the first embodiment] As explained above, the generation device 30 has a receiving unit 31 and a combining unit 32. The receiving unit 31 receives input of an input file that defines information for executing configuration input for communication devices that accommodate users who use the network, and that differs depending on the model of the communication device. The combining unit 32 combines the input file with a common definition file that defines information common to the model of the communication device, and that is information for executing configuration input for the communication device.

[0092] According to the generation device 30, data to be added to the command conversion unit can be automatically obtained, so that data for inputting commands to the communication device can be obtained efficiently.

[0093] The receiving unit 31 also receives an input file in which a command group that differs depending on the model of the communication device is described. The combining unit 32 combines the input file with a common definition file that defines a process for calling a command included in the command group.

[0094] The receiving unit 31 also receives an input of an input file in which commands to be called in the execution of a task are written.

[0095] Furthermore, the synthesis unit 32 synthesizes a common definition file including information for identifying a task corresponding to a specified scenario with the input file.

[0096] The receiving unit 31 also receives an input of an input file that further describes an error detection process that occurs when a command is executed.

[0097] In this way, the generation device 30 divides the functional deployment of the command conversion unit into model-dependent functional units (parts derived from the input file) and parts commonly used within the model (parts derived from the common definition file), thereby precisely separating the difference information for each model.

[0098] The receiving unit 31 also receives input of an input file containing information on variables used in commands called in the execution of a task, a response message when the command is executed successfully, the contents of repetitive processing, the contents of branching processing, and parameters updated in the execution of a command.

[0099] In this way, by formatting command files for each model and presenting a method that allows for description of repetitive processing and branching conditions, it is possible to clarify a framework that can be automatically generated based on data entered into the format.

[0100] [System configuration, etc.] Furthermore, the components of each device shown in the figure are conceptual functional units and do not necessarily have to be physically configured as shown. In other words, the specific form of distribution and integration of each device is not limited to that shown, and all or part of the devices can be functionally or physically distributed or integrated in any unit depending on various loads, usage conditions, etc. Furthermore, all or any part of the processing functions performed by each device can be realized by a CPU and a program analyzed and executed by the CPU, or can be realized as hardware using wired logic.

[0101] Furthermore, among the processes described in this embodiment, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method.In addition, the information including the processing procedures, control procedures, specific names, various data and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified.

[0102] [program] In one embodiment, the generating device 30 can be implemented by installing a generating program that executes the above-described generating process as package software or online software on a desired computer. For example, by causing an information processing device to execute the above-described generating program, the information processing device can function as the generating device 30. The information processing device referred to here includes desktop and notebook personal computers. In addition, the information processing device also includes mobile communication terminals such as smartphones, mobile phones, and PHS (Personal Handyphone Systems), as well as slate terminals such as PDAs (Personal Digital Assistants).

[0103] 12 is a diagram showing an example of a computer that executes a generation program. The computer 1000 includes, for example, a memory 1010 and a CPU 1020. The computer 1000 also includes 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.

[0104] 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 1090. The disk drive interface 1040 is connected to a disk drive 1100. A removable storage medium such as a magnetic disk or 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, a display 1130.

[0105] The hard disk drive 1090 stores, for example, an OS 1091, an application program 1092, a program module 1093, and program data 1094. That is, a program that defines each process of the generation device 30 is implemented as a program module 1093 in which computer-executable code is written. The program module 1093 is stored, for example, in the hard disk drive 1090. For example, a program module 1093 for executing processes similar to those of the functional configuration of the generation device 30 is stored in the hard disk drive 1090. Note that the hard disk drive 1090 may be replaced with an SSD.

[0106] Furthermore, setting data used in the processing of the above-described embodiment is stored as program data 1094, for example, in the memory 1010 or the hard disk drive 1090. Then, the CPU 1020 reads the program module 1093 or the program data 1094 stored in the memory 1010 or the hard disk drive 1090 into the RAM 1012 as necessary, and executes the processing of the above-described embodiment.

[0107] The program module 1093 and program data 1094 are not limited to being stored in the hard disk drive 1090, but may also 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 program data 1094 may be stored in another computer connected via a network (such as a local area network (LAN) or a wide area network (WAN)). The program module 1093 and program data 1094 may then be read by the CPU 1020 from the other computer via the network interface 1070. [Explanation of symbols]

[0108] 1 Management System 2. Upper system 10 Management device 11 Upper system support section 12 Configuration input request management DB 13 Decision Section 20A, 20B, 20B´, 20C Edge 30 Generator 31 Reception 32 Synthesis section 14A, 14B, 14C Device control section 141A, 141B, 141C common control section 142A, 142B, 142C Individual control units 143A, 143B Command conversion section 143C Edge Control Device 1431B Common processing section 1431B_1, 1431B_2 Model-specific processing unit

Claims

1. a receiving unit that receives input of a first file that defines information for executing configuration input for a communication device that accommodates a user who uses a network, the information differing depending on the model, version, and use of the communication device; a synthesizing unit that synthesizes the first file with a second file that defines information for executing configuration input to the communication device and that is common to the model, version, and use of the communication device; A generating device comprising:

2. the receiving unit receives input of the first file in which a group of commands that differ depending on the model, version, and purpose of the communication device are described; The generating device according to claim 1 , wherein the combining unit combines the second file, in which a process for calling a command included in the command group is defined, with the first file.

3. the receiving unit receives input of the first file in which a command to be called in the execution of a task is written; The generating device according to claim 1 , wherein the combining unit combines the second file containing information for identifying a task corresponding to a specified scenario with the first file.

4. 4. The generating device according to claim 3, wherein the receiving unit receives input of the first file, which further describes an error detection process that is performed when a command is executed.

5. The generation device described in claim 3, characterized in that the reception unit receives input of the first file including information on variables used in commands called in task execution, a response message when the command is executed successfully, the contents of repetitive processing, the contents of branching processing, and parameters updated in command execution.

6. A generation method performed by a generation device, comprising: a receiving step of receiving input of a first file defining information for executing configuration input for a communication device accommodating a user who uses a network, the information differing depending on the model, version, and use of the communication device; a combining step of combining the first file with a second file that defines information for executing configuration input to the communication device and that is common to the model, version, and use of the communication device; A generating method comprising:

7. a receiving step of receiving an input of a first file that defines information for executing configuration input for a communication device that accommodates a user who uses a network, the information differing depending on the model, version, and use of the communication device; a combining step of combining the first file with a second file that defines information for executing configuration input for the communication device and that is common to the model, version, and use of the communication device; A generating program that causes a computer to execute the above.

Images