CONFIG INPUT DEVICE, CONFIG INPUT METHOD, AND CONFIG INPUT PROGRAM

The configuration input device and method simplify tunnel configuration management by dividing processes into templates and storing them in a storage unit, enabling easy and flexible configuration creation and management.

JP7589792B2Active Publication Date: 2024-11-26NIPPON TELEGRAPH & TELEPHONE CORP
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
JP2023500159
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2021-02-16
Publication Date
2024-11-26
Estimated Expiration
2041-02-16

AI Technical Summary

Technical Problem

Creating configurations for tunnel settings for each user and each device generates a huge number of configuration patterns, making configuration creation and management complicated.

Method used

A configuration input device and method that includes an order reception unit, first and second configuration processes, a third setting process for tunnel interfaces, and a fourth process for interface parameters, dividing configuration processes into templates and storing them in a storage unit, and a configuration processing unit to create and input configurations to transfer devices.

Benefits of technology

Facilitates easy creation and management of tunnel configurations, allowing for flexible and efficient configuration management and partial changes.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007589792000001
    Figure 0007589792000001
  • Figure 0007589792000002
    Figure 0007589792000002
  • Figure 0007589792000003
    Figure 0007589792000003
Patent Text Reader

Abstract

When receiving a setting order for a tunnel from an upper Ops (operation system), a controller (10) divides the setting order into a first setting process related to user setting and registration, a second setting process related to a forwarding plane of the tunnel, a third setting process related to interfaces of respective forwarding devices used for the tunnel of the forwarding plane, and a fourth setting process related to parameters to be processed to set for the interfaces, and stores the setting processes in an setting management DB (113). Next, the controller (10) generates configurations for executing the respective setting processes indicated by the setting order for the tunnel by applying information indicated by the respective divided setting processes to templates of the respective setting processes. Then, the controller (10) inputs the generated configurations to the forwarding devices (40) for which the tunnel is to be set.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

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

[0002] Conventionally, when a network controller receives a tunnel setting order from a certain user, it creates and inputs a configuration for the tunnel start point device and end point device of the user based on the setting order. [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] IP in IP Tunneling, [Retrieved January 29, 2021], Internet<URL:https: / / tools.ietf.org / html / rfc1853> [Non-Patent Document 2] Generic Routing Encapsulation (GRE), [Retrieved January 29, 2021], Internet<URL:https: / / tools.ietf.org / html / rfc2784> Summary of the Invention [Problem to be solved by the invention]

[0004] However, creating a configuration for tunnel setting for each user and each device generates a huge number of setting patterns, which complicates the creation and management of the configuration. Therefore, an object of the present invention is to solve the above-mentioned problems and to facilitate the creation and management of a configuration for tunnel setting to each device in a network. [Means for solving the problem]

[0005] In order to solve the above-mentioned problems, the present invention is characterized by comprising an order receiving unit that receives a tunnel setting order, an order dividing unit that divides the tunnel setting order into a first setting process related to a user's setting registration, a second setting process related to a forwarding plane of the tunnel, a third setting process related to an interface of each forwarding device used for the tunnel on the forwarding plane, and a fourth setting process related to parameters to be set to the interfaces, and stores the divided process in a memory unit, a setting processing unit that creates a configuration for executing the tunnel setting process indicated in the setting order by reflecting information indicated in each of the setting processes in a template prepared for each of the setting processes, and a configuration input unit that inputs the configuration to the forwarding device to which the tunnel is to be set. Effect of the Invention

[0006] According to the present invention, it is possible to easily create and manage configurations for setting tunnels in each device in a network. [Brief description of the drawings]

[0007] [Figure 1] FIG. 1 is a diagram illustrating an example of a network configured by a transfer device. [Diagram 2] FIG. 2 is a diagram illustrating an example of the configuration of a system including a controller. [Diagram 3] FIG. 3 is a diagram for explaining an overview of the setting unit in FIG. [Figure 4] FIG. 4 is a diagram showing an example of the setting process stored in the setting management DB of FIG. [Diagram 5] FIG. 5 is a diagram for explaining a template used by the controller of FIG. [Figure 6] FIG. 6 is a diagram for explaining an overview of the device determination unit in FIG. [Figure 7] FIG. 7 is a diagram showing an example of device information stored in the device information DB of FIG. [Figure 8] FIG. 8 is a flowchart illustrating an example of a processing procedure of the controller of FIG. [Figure 9] FIG. 9 is a flowchart showing an example of the processing procedure in S106 of FIG. [Figure 10] FIG. 10 is a sequence diagram illustrating an example of a processing procedure of the controller of FIG. [Figure 11] FIG. 11 is a sequence diagram illustrating an example of a processing procedure of the controller of FIG. [Figure 12] FIG. 12 is a diagram illustrating an example of the configuration of a computer that executes a configuration input program. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, a mode (embodiment) for carrying out the present invention will be described with reference to the drawings. The present invention is not limited to the embodiment described below.

[0009] [Transporter and Controller] First, the transfer device 40 to which the controller 10 inputs a configuration will be described with reference to FIG.

[0010] The transfer device 40 is a device that transfers data at L2 (layer 2) or L3 (layer 3), and is communicably connected via a network (see reference numeral 101 in FIG. 1). Each of the transfer devices 40 has a tunnel function, and when a tunnel is set between the transfer device 40 and another transfer device 40, the transfer device 40 transfers data using the tunnel. In the following description, the tunnel may be an L3 tunnel or an L2 tunnel.

[0011] 1, the NW#1 and NW#2 of user A are connected by a tunnel set up between the transfer devices 40 (logical NW#A). In addition, for example, the NW#1 and NW#2 of user B are also connected by a tunnel set up between the transfer devices 40 (logical NW#B).

[0012] Here, for example, consider a case where a tunnel is added to the logical NW#B as shown by reference numeral 103 due to an increase in the amount of communication between NW#1 and NW#2 of user B. In this case, as shown by reference numeral 104, the controller 10 of the transfer device 40 inputs a configuration for adding a tunnel to the transfer device 40 constituting the logical NW#B.

[0013] [System configuration example] Next, a configuration example of a system including the controller 10 will be described with reference to Fig. 2. The system 1 includes, for example, the controller 10, a real-time information DB (database) 20, an external information collection system 30, and transfer devices 40 (40A, 40B, ..., 40N).

[0014] The controller 10 is a device that controls each transfer device 40. For example, when the controller 10 receives an order to set up a tunnel between the transfer devices 40 from an upper Ops (operation system), the controller 10 creates a configuration for setting up the tunnel by referring to information collected from the real-time information DB 20, the external information collection system 30, etc. Then, the controller 10 inputs the created configuration into the transfer device 40 where the tunnel is to be set up.

[0015] The real-time information DB 20 stores information indicating the communication status between each transfer device 40. The information indicating the communication status between the transfer devices 40 is, for example, information indicating the communication delay time, jitter, communication bandwidth, etc. between each transfer device 40. The information in the real-time information DB 20 is updated, for example, at predetermined intervals.

[0016] The external information collection system 30 collects information on the communication status (e.g., communication delay time, jitter, communication bandwidth, etc.) between each transfer device 40. For example, based on a request from the controller 10, the external information collection system 30 collects information on the communication status between designated transfer devices 40 and outputs the information to the controller 10.

[0017] [controller] The controller 10 includes a setting unit 11 and a device determination unit 12. The setting unit 11 creates a configuration for tunnel setting and inputs it to the transfer device 40 to which the tunnel is to be set. The device determination unit 12 determines the transfer device 40 to which the configuration by the setting unit 11 is to be input, based on information indicating the communication status between the transfer devices 40, communication requirements of the tunnel user (user requirements), and the like.

[0018] [Settings section] The setting unit 11 includes an order receiving unit 111, an order dividing unit 112, a setting management DB 113, a template DB 114, a setting processing unit 115, and a configuration input unit 116. The setting management DB 113 and the template DB 114 are provided in a storage unit (not shown) of the controller 10.

[0019] First, an overview of the setting unit 11 will be described with reference to Fig. 3. As shown in Fig. 3, the order receiving unit 111 of the setting unit 11 receives, for example, a tunnel setting order from an upper Ops (S1). Thereafter, the order dividing unit 112 divides the setting order received in S1 (S2) and stores it in the setting management DB 113 (S3). Thereafter, the setting processing unit 115 reads out the setting process from the setting management DB 113 and processes it (S4).

[0020] Next, returning to Fig. 2, the setting unit 11 will be described in detail. The order receiving unit 111 of the setting unit 11 receives a tunnel setting order. The tunnel setting order includes, for example, any one of the setting processes shown in the following (1) to (4) or a combination of these.

[0021] (1) Registering or deleting a tunnel user (2) Setting up and deleting a forwarding plane using a tunnel (3) Setting up, deleting, or changing the settings of a tunnel interface (4) Changing the parameters associated with each interface

[0022] Among the setting orders, the information related to the setting process (1) includes, for example, a user ID, etc. The information related to the setting process (2) includes, for example, the type of forwarding plane (e.g., L3 or L2), device information used in the forwarding plane (e.g., the device ID of the forwarding device 40), etc. The information related to the setting process (3) includes, for example, the type of tunnel, the IP address of the interface used in the tunnel, etc. The information related to the setting process (4) includes the type of parameters to be set (e.g., BGP (Border Gateway Protocol), QoS (Quality of Service), endpoint addresses, etc.), parameter values, etc.

[0023] The order dividing unit 112 divides the setting order received by the order receiving unit 111 into a predetermined setting process unit. For example, the order dividing unit 112 divides the setting order into the setting processes shown in (1) to (4) above. Thereafter, the order dividing unit 112 stores the divided setting processes in the setting management DB 113.

[0024] The order division unit 112 divides the setting order into the setting processes shown in (1) to (4) above, as shown in FIG. 4, for example, and stores the mutually related setting processes in a tree structure in the setting management DB 113.

[0025] This tree structure, as shown in FIG. 4, is connected in the following order from the top of the tree to the bottom: (1) user-related setting process → (2) forwarding-related setting process → (3) interface-related setting process → (4) parameter-related setting process.

[0026] Returning to the explanation of Fig. 2, the setting management DB 113 stores the setting orders divided by the order dividing unit 112 into setting processing units (see Fig. 4).

[0027] The template DB 114 stores templates for executing each setting process stored in the setting management DB 113. For example, the template DB 114 stores templates for sequentially executing the setting processes (1) to (4) described above.

[0028] The setting processing unit 115 creates a configuration for executing the setting process indicated in the setting order by reflecting the information indicated for each setting process divided by the order dividing unit 112 in a template for executing the setting process read from the template DB 114.

[0029] For example, the setting processing unit 115 creates a configuration by reflecting elements in the tree (see FIG. 4) of each divided setting process in order from the top to the bottom in the template corresponding to the setting processes (1) to (4) read from the template DB 114.

[0030] As an example, the setting processing unit 115 creates a configuration that executes settings in the following order, as shown in FIG. 5: (1) user registration process → (2) new forwarding plane creation process → (3) interface creation and tunnel creation process → (4) parameter setting and change process.

[0031] The creation of an interface in (3) is, for example, the creation of a tunnel IF or a VLAN-IF, and the setting and changing of parameters in (4) is, for example, the change of BGP or the like, or the change of parameters of QoS, filters, etc.

[0032] Furthermore, the setting processing unit 115 requests the device determination unit 12 to determine the transfer device 40 (setting device) to which the configuration is to be input.

[0033] For example, the setting processing unit 115 outputs a setting device determination request including parameters included in the tunnel setting order to the device determination unit 12. Note that these parameters are, for example, a user ID, a tunnel type, a setting amount (for example, a bandwidth used by the tunnel), a device ID or IP address of a transfer device 40 that is a setting candidate for the tunnel, and network information of a connection destination of the transfer device 40. For example, the contents of the setting process read by the setting processing unit 115 from the setting management DB 113 may be used as these parameters.

[0034] Then, when the setting processing unit 115 receives the determination result of the transfer device 40 to which the configuration is to be input from the device determination unit 12, the setting processing unit 115 requests the configuration input unit 116 to input the configuration to the transfer device 40. The configuration input unit 116 inputs the configuration to the transfer device 40 based on the request from the setting processing unit 115.

[0035] [Device determination section] Next, a description will be given of the device determination unit 12. The device determination unit 12 includes a requirement receiving unit 121, a user requirement DB 122, a real-time information acquiring unit 123, a device information DB 124, and a device determination processing unit 125. The user requirement DB 122 and the device information DB 124 are provided in a storage unit (not shown) of the controller 10.

[0036] First, an overview of the device determination unit 12 will be described with reference to Fig. 6. As shown in Fig. 6, when a requirement receiving unit 121 of the device determination unit 12 receives a user requirement (a user's communication requirement), the requirement receiving unit 121 stores the user requirement in a user requirement DB 122 (S11).

[0037] After S11, when the device determination processing unit 125 receives a setting device determination request including the above parameters from the setting processing unit 115 (see FIG. 2), the device determination processing unit 125 selects a compatible candidate device (transfer device 40 that is a candidate for the setting device) from the device information DB 124 (S12).

[0038] For example, the device determination processing unit 125 selects a candidate device based on the above parameters, the types of tunnels that each transfer device 40 can handle and the resource status (for example, resource upper limit amount, consumed resources, etc.) indicated in the device information DB 124.

[0039] After S12, the real-time information acquisition unit 123 acquires information indicating the communication status of the candidate device selected in S12 from the real-time information DB 20 or the external information collection system 30 (S13).

[0040] For example, when the candidate devices are transfer devices #1 to #4 shown in FIG. 6, the real-time information acquisition unit 123 acquires information such as delay, jitter, and bandwidth of communication between each of the transfer devices #1 to #4.

[0041] After S13, the device determination processing unit 125 determines a setting device from among the candidate devices selected in S12, using information indicating the communication status of the candidate devices and user requirements (S14).

[0042] For example, the device determination processing unit 125 determines, as setting devices, the transfer device #1 and the transfer device #4 that satisfy the user conditions from among the transfer devices #1 to #4, using information indicating the communication status of the candidate devices indicated by the reference numeral 601 and the user conditions indicated by the reference numeral 602. Then, the device determination processing unit 125 outputs information on the determined transfer device #1 and the transfer device #4 to the setting processing unit 115.

[0043] Returning to Fig. 2, the device determination unit 12 will be described in detail. When the requirements receiving unit 121 of the device determination unit 12 receives input of user requirements, it stores them in the user requirements DB 122. The user requirements DB 122 stores the user requirements. The user requirements are information indicating the communication requirements of each user. For example, as shown by reference numeral 602 in Fig. 6, the user requirements are information indicating, for each user, the amount of delay (delay time) permitted for the communication of the user, the guaranteed bandwidth value (guaranteed bandwidth), and the like.

[0044] The real-time information acquisition unit 123 acquires information indicating the communication status between each transfer device 40. The information indicating the communication status between each transfer device 40 is, for example, information indicating the delay time, traffic volume, etc. for each section connecting the transfer devices 40, as shown by reference numeral 601 in Fig. 6. The information is acquired in real time from each transfer device 40, for example.

[0045] The device information DB 124 stores device information of each transfer device 40. The device information is information that indicates the amount of allocated resources and the amount of resource consumption of the transfer device 40.

[0046] The device information is, for example, as shown in FIG. 7, information indicating the device ID, model, OS (Operating System) version, supported tunnel types, resource upper limit amount, consumed resources, and the like of the transfer device 40.

[0047] The resource upper limit amount is information indicating, for example, the upper limit of the number of users of a tunnel, the upper limit of the number of tunnels, etc. that can be set in the transfer device 40. The consumed resource amount is information indicating, for example, the number of users of a tunnel, the number of tunnels, etc. that are set in the transfer device 40.

[0048] Returning to the explanation of Fig. 2, the device determination processing unit 125 determines a setting device based on a setting device determination request output from the setting processing unit 115. This setting device determination request includes parameters included in the tunnel setting order. For example, the parameters are contents indicated in each setting process read by the setting processing unit 115 from the setting management DB 113.

[0049] As described above, the parameters are, for example, a user ID, a tunnel type, a setting amount, a device ID or IP address of a transfer device 40 that is a tunnel setting candidate, or destination network information.

[0050] For example, the device determination processing unit 125 determines, as a setting device, a transfer device 40 that satisfies the communication requirements of the user from among the transfer devices 40 that are candidates for setting the tunnel, based on the user ID and the transfer device 40 that are candidates for setting the tunnel included in the above parameters, the allocated resource amount and the consumed resource amount of each transfer device 40 indicated in the device information of the device information DB 124, and information indicating the communication status between each transfer device 40 collected by the real-time information acquisition unit 123. Then, the device determination processing unit 125 outputs the transfer device 40 determined as the setting device to the setting processing unit 115.

[0051] According to such a controller 10, the tunnel setting order is divided into multiple setting processes, and the configuration is created using a template, so that the configuration can be created easily. Also, the controller 10 stores the divided setting processes in the setting management DB 113 in, for example, a tree structure. This makes it easier to manage the configuration and to make partial changes or expansions.

[0052] Furthermore, the controller 10 determines the transfer device 40 that satisfies the user's communication requirements as the destination of the configuration, using the communication status between each transfer device 40. This allows the controller 10 to flexibly determine the transfer device 40 as the destination of the tunnel setting in accordance with the communication status between each transfer device 40.

[0053] [Example of processing procedure] Next, an example of a processing procedure of the controller 10 will be described with reference to Fig. 8. For example, first, the order receiving unit 111 of the controller 10 receives a tunnel setting order from an upper Ops (S101). Next, the order dividing unit 112 divides the setting order received in S101 into multiple setting processes (S102: dividing the setting order). Then, the order dividing unit 112 stores the divided setting processes in the setting management DB 113 (S103).

[0054] After S103, the setting processing unit 115 reads out the setting process from the setting management DB 113 (S104). The setting processing unit 115 also requests the device determination unit 12 to determine the transfer device 40 (setting device) to which the configuration is to be input (S105).

[0055] After S105, the device determination unit 12 determines the transfer device 40 to which the configuration is to be input based on the request (S106). Details of the processing of S106 will be described later. Then, the setting processing unit 115 uses the template in the template DB 114 to create a configuration that reflects the setting processing read out in S104 (S107). Thereafter, the configuration input unit 116 inputs the configuration created in S107 to the transfer device 40 determined in S106 (S108).

[0056] Next, S106 in Fig. 8 will be described in detail with reference to Fig. 9. First, the device determination processing unit 125 of the device determination unit 12 receives a setting device determination request (S121). As described above, this setting device determination request includes parameters included in the tunnel setting order (e.g., user ID, tunnel type, setting amount, device ID or IP address of the transfer device 40 that is a tunnel setting candidate, or destination network information, etc.).

[0057] After S121, the device determination processing unit 125 acquires device information of the transfer device 40 that is a tunnel setting candidate included in the parameters of the setting device determination request from the device information DB 124 (S122). Then, the device determination processing unit 125 determines, based on the acquired device information, for each of the transfer devices 40 that is a tunnel setting candidate, whether or not it can handle a tunnel of the type indicated in the above parameters (S123: Supportable type of tunnel?) and whether or not there are available resources (S124).

[0058] For example, the device determination processing unit 125 selects one of the transfer devices 40 that are candidates for tunnel setting, and determines whether or not the transfer device 40 can handle a tunnel of the type indicated in the above parameters (S123: Supported type of tunnel?) and whether or not there are available resources (S124). Then, if there is an unselected transfer device 40 that is a candidate for setting (S125: Other candidates? → Yes), the device determination processing unit 125 executes the processes of S123 and S124 for the transfer device 40 that is the unselected transfer device that is a candidate for setting.

[0059] On the other hand, if there is no unselected transfer device 40 that is a setting candidate (S125: Are there other candidates? → No), the device determination processing unit 125 determines whether there is a transfer device 40 that satisfies the requirements indicated by the above parameters (S126). Here, if the device determination processing unit 125 determines that there is no transfer device 40 that satisfies the requirements (S126 → No), it returns NG to the setting processing unit 115 (S137).

[0060] On the other hand, if the device determination processing unit 125 determines that there is a transfer device 40 (candidate device) that satisfies the requirements indicated in the above parameters (S126 → Yes), it requests information indicating the communication status of the candidate device from the real-time information acquisition unit 123 (S131: information request).

[0061] After S131, if the real-time information acquisition unit 123 has information indicating the communication status of the candidate device in the real-time information DB 20 (S132: Information in DB?→Yes), it outputs the information to the device determination processing unit 125. As a result, the device determination processing unit 125 receives the information indicating the communication status of the candidate device (S134).

[0062] On the other hand, if the real-time information DB 20 does not contain information indicating the communication status of the candidate device (S132: Information in DB?→No), the real-time information acquisition unit 123 requests the external information collection system 30 to acquire the information (S133). Then, when the real-time information acquisition unit 123 acquires the information from the external information collection system 30, it outputs the information to the device determination processing unit 125. As a result, the device determination processing unit 125 receives the information indicating the communication status of the candidate device (S134).

[0063] After S134, the device determination processing unit 125 compares the information received in S134 with the user requirements to determine whether or not there is a candidate device that satisfies the user requirements (S135). If the device determination processing unit 125 determines that there is a candidate device that satisfies the user requirements (S135→Yes), it returns device information (e.g., device ID, IP address, etc.) of the candidate device that satisfies the user requirements to the setting processing unit 115 (S136).

[0064] On the other hand, if the device determination processing unit 125 determines that there is no candidate device that satisfies the user requirements (S135→No), it returns NG to the setting processing unit 115 (S137).

[0065] Next, an example of a processing procedure of the device determination unit 12 will be described with reference to the sequence diagram shown in Fig. 10. For example, when the requirement receiving unit 121 of the device determination unit 12 receives an input of a user requirement from an upper Ops (S141), the requirement is registered in the user requirement DB 122 (S142).

[0066] After S142, the device determination processing unit 125 receives a request to determine a setting device for the tunnel from the setting processing unit 115 (S143). As described above, this setting device determination request includes parameters included in the setting order (e.g., user ID, tunnel type, list of transfer devices 40 that are candidates for setting the tunnel (device ID, IP address, etc.)).

[0067] After S143, the device determination processing unit 125 acquires device information of the transfer device 40 that is a setting candidate, which is included in the above parameters, from the device information DB 124 (S144). Then, the device determination processing unit 125 selects a candidate device using the device information acquired in S144 (S145).

[0068] For example, based on the device information acquired in S144, the device determination processing unit 125 selects, from the transfer device 40 that is a candidate for setting, a transfer device 40 that can handle the tunnel type indicated by the above parameters and has available resources, as a candidate device.

[0069] After S145, the device determination processing unit 125 requests the real-time information acquisition unit 123 for information indicating the communication status of the candidate device selected in S145 (S146: information request). Then, the real-time information acquisition unit 123 acquires information indicating the communication status of the candidate device based on the request (S147). For example, the real-time information acquisition unit 123 first searches the real-time information DB 20 for information indicating the communication status of the candidate device. Here, if there is no information in the real-time information DB 20, the real-time information acquisition unit 123 requests the external information collection system 30 to acquire information indicating the communication status of the candidate device, and acquires the information indicating the communication status of the candidate device.

[0070] After S147, the real-time information acquisition unit 123 returns information to the device determination processing unit 125 (S148). For example, the real-time information acquisition unit 123 outputs to the device determination processing unit 125 the information indicating the communication status of the candidate device acquired in S147.

[0071] After S148, the device determination processing unit 125 acquires user requirements corresponding to the user ID included in the above parameters from the user requirement DB 122 (S149). Then, the device determination processing unit 125 compares the answer (information indicating the communication status of the candidate device) acquired in S148 with the user requirements acquired in S149, and determines the candidate device that satisfies the user requirements as the setting device (S150: determination of setting device). Then, the device determination processing unit 125 responds to the setting processing unit 115 with the device information of the setting device determined in S150 (S151).

[0072] Next, the process after the setting processing unit 115 receives the response of the device information of the setting device in S151 of FIG. 10 will be described with reference to the sequence diagram shown in FIG.

[0073] The setting processing unit 115 reads device information of the setting device (e.g., information on the model and OS of the setting device) from the device information DB 124 based on the device information of the setting device received from the device determination processing unit 125 (e.g., the device ID and IP address of the setting device) (S161). Next, the setting processing unit 115 reads a template from the template DB 114 (S162). Then, the setting processing unit 115 creates a configuration to be input to the setting device by reflecting each setting process stored in the setting management DB 113 and the device information of the setting device read in S161 in the template read in S162 (S163).

[0074] After S163, the setting processing unit 115 makes a request to the configuration input unit 116 to input the configuration created in S163 (S164: configuration request). Then, based on the input request, the configuration input unit 116 inputs the configuration created in S163 to the transfer device 40 (for example, transfer device #1) that is the setting device of the configuration (S165: configuration input). After that, when the configuration input unit 116 receives a result notification of the input of the configuration (S166), it updates the device information in the device information DB 124 based on the result notification (S167). For example, the setting processing unit 115 updates the value of the consumed resource in the device information (see FIG. 7) related to the transfer device 40 to which the configuration is input.

[0075] According to such a controller 10, the tunnel setting order is divided into multiple setting processes, and the configuration is created using a template, so that the configuration can be created easily. Also, the controller 10 stores the divided setting processes in the setting management DB 113 in, for example, a tree structure. This makes it easier to manage the configuration and to make partial changes or expansions.

[0076] Furthermore, the controller 10 determines the transfer device 40 that satisfies the user's communication requirements as the destination of the configuration, using the communication status between each transfer device 40. This allows the controller 10 to flexibly determine the transfer device 40 as the destination of the tunnel, depending on the communication status between each transfer device 40.

[0077] [System configuration, etc.] In addition, each component of each unit shown in the figure is a functional concept, and does not necessarily have to be physically configured as shown in the figure. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or a part of it can be functionally or physically distributed and integrated in any unit according to various loads, usage conditions, etc. Furthermore, each processing function performed by each device can be realized in whole or in part by a CPU and a program executed by the CPU, or can be realized as hardware using wired logic.

[0078] Furthermore, among the processes described in the above embodiments, 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 by 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 arbitrarily unless otherwise specified.

[0079] [program] The controller 10 can be implemented by installing a program as package software or online software on a desired computer. For example, the program can be executed by an information processing device, causing the information processing device to function as the controller 10. The information processing device here includes desktop or notebook personal computers. In addition, the information processing device also includes mobile communication terminals such as smartphones, mobile phones, and PHS (Personal Handyphone System), and further terminals such as PDAs (Personal Digital Assistants).

[0080] The controller 10 may also be implemented as a server device that provides services related to the above-mentioned processes to a client, the client being a terminal device used by a user. In this case, the server device may be implemented as a Web server, or may be implemented as a cloud that provides services related to the above-mentioned processes by outsourcing.

[0081] 12 is a diagram showing an example of a computer that executes a configuration input 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 components is connected by a bus 1080.

[0082] The memory 1010 includes a read only memory (ROM) 1011 and a random access memory (RAM) 1012. The ROM 1011 stores a boot program such as a basic input output system (BIOS). 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 an optical disk is inserted into the disk drive 1100. The serial port interface 1050 is connected to a mouse 1110 and a keyboard 1120, for example. The video adapter 1060 is connected to a display 1130, for example.

[0083] 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, the programs that define each process executed by the controller 10 are implemented as program modules 1093 in which computer-executable codes are written. The program modules 1093 are stored, for example, in the hard disk drive 1090. For example, the program modules 1093 for executing processes similar to those of the functional configuration in the controller 10 are stored in the hard disk drive 1090. The hard disk drive 1090 may be replaced by an SSD (Solid State Drive).

[0084] Data used in the processing of each of the above-described embodiments is stored as program data 1094 in, for example, the memory 1010 or the hard disk drive 1090. Then, the CPU 1020 reads out 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 them.

[0085] Note that the program module 1093 and the program data 1094 are not limited to being 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 (such as a local area network (LAN) or wide area network (WAN)). The program module 1093 and the program data 1094 may then be read by the CPU 1020 from the other computer via the network interface 1070. [Explanation of symbols]

[0086] 1 System 10 Controller 11 Setting section 12 Device determination section 20 Real-time information DB 30 External information gathering system 40 Teleporter 111 Order Reception Department 112 Order division section 113 Settings management DB 114 Template DB 115 Setting processing section 116 Configuration input section 121 Requirements Reception Department 122 User requirements DB 123 Real-time information acquisition unit 124 Device information DB

Claims

1. an order receiving unit that receives an order for setting up a tunnel; an order division unit that divides the tunnel setting order into a first setting process related to user setting registration, a second setting process related to a forwarding plane of the tunnel, a third setting process related to an interface of each forwarding device used for the tunnel of the forwarding plane, and a fourth setting process related to parameters to be set in the interface, and stores the mutually related setting processes in a tree structure in a storage unit; a setting processing unit that creates a configuration for executing the tunnel setting processes indicated in the setting order in the order from the highest setting process in the tree structure of the setting processes by reflecting information indicated in each of the setting processes in a template prepared for each of the setting processes; a configuration input unit that inputs the configuration to a forwarding device that is a destination of the tunnel; A configuration input device comprising:

2. a device determination unit that determines a transfer device that satisfies a communication requirement of the user among the transfer devices that are candidates for setting the tunnel as a transfer device to which the tunnel is to be set, based on identification information of a user of the tunnel, a transfer device that is a candidate for setting the tunnel, and information indicating a communication status between the transfer devices, which are included in the tunnel setting order; The setting processing unit: Create the configuration to be input to the forwarding device to which the determined tunnel is to be set.

2. The configuration input device according to claim 1 .

3. The user's communication requirements are: The tunnel-based communication protocol includes at least one of the delay time and the communication bandwidth that is permitted for the user's communication using the tunnel.

3. The configuration input device according to claim 2.

4. A configuration input method executed by a configuration input device, comprising: receiving an order for establishing a tunnel; a step of dividing the tunnel setting order into a first setting process related to user setting registration, a second setting process related to a forwarding plane of the tunnel, a third setting process related to an interface of each forwarding device used for the tunnel of the forwarding plane, and a fourth setting process related to parameters to be set in the interface, and storing the mutually related setting processes in a tree structure in a storage unit; creating a configuration for executing the tunnel setting processes indicated in the setting order in the order from the highest setting process in the tree structure of the setting processes by reflecting information indicated in each of the setting processes in a template prepared for each of the setting processes; inputting the configuration into a forwarding device to which the tunnel is set; A configuration input method comprising:

5. receiving an order for establishing a tunnel; a step of dividing the tunnel setting order into a first setting process related to user setting registration, a second setting process related to a forwarding plane of the tunnel, a third setting process related to an interface of each forwarding device used for the tunnel of the forwarding plane, and a fourth setting process related to parameters to be set in the interface, and storing the mutually related setting processes in a tree structure in a storage unit; creating a configuration for executing the tunnel setting processes indicated in the setting order in the order from the highest setting process in the tree structure of the setting processes by reflecting information indicated in each of the setting processes in a template prepared for each of the setting processes; inputting the configuration into a forwarding device to which the tunnel is set; A configuration input program that causes a computer to execute the above.

Citation Information

Patent Citations

  • Communication system and program

    JP2014160907A

  • Method and system for implementing a virtual private network based on a traffic engineering tunnel

    JP2014532368A

  • Method, device, and program for management and orchestration of network functions virtualization

    WO2016117697A1