JP4460396B2 - Script generation device, script generation method, and script generation program - Google Patents

Description

  The present invention relates to a script generation device, a script generation method, and a script generation program, and in particular, when a device having an interface for exchanging programs by an interactive application connects to a new connection destination, the device currently has It is suitable for application to a method of reconstructing a script that confirms the consistency of whether or not a script description can be diverted and, if a difference in script description is found, returns an expected response by repeating trials.

For example, applications such as telnet, ftp, passwd, fsck, rlogin, and tip are used for communication between devices connected to a network.
Further, for example, Non-Patent Document 1 teaches the input expected from the dialogue program for such an application and the correct response to the input, so that software can be used without any human instruction. An automated technique for talking to a dialogue program is disclosed.

Further, for example, in Patent Document 1, in dialog control used for an interactive interface for controlling a device, a dialog that can be changed according to a user's system usage frequency or a user's preference regarding dialog progress can be adjusted. A method for realizing efficient dialogue by a control method is disclosed.
Also, for example, in Patent Document 2, a mark sheet having a new configuration is used, and a mark sheet is generated according to the situation to provide an interactive interface, improving the operability of the operator and reducing the learning burden of the operation method. A method of mitigating is disclosed.

  On the other hand, in a network service, a network element (Network Element) in which a new function is implemented is generally added or renewed. At the same time, a network management apparatus that collects and processes information and a server group that operates services are provided with an interface function with a network element.

  Here, these network management devices and server groups must be managed by networks manufactured by different vendors and configured by connecting a plurality of multi-vendor network elements having different interfaces. For this reason, a configuration is adopted in which the core function of the software and the vendor-dependent unit are separated and the interface is switched according to the connection destination. As a result, even when a new network element is released or an operating system is renewed, the operation can be continued only by additional development of an adapter corresponding to the network element.

Here, at the start of the network service, it is preferable to be able to release the network management device together with the network element. For this purpose, the network management device interface is designed simultaneously with the design of the new function of the network element. It is necessary to match the specifications.
Lives, D.M. , Expect: Curing This Uncontrollable Fits of Interaction, Proceedings of the summer, 1990 USENIX Conference, Anaheim, CA, June 11-15, 1990-Discussion. From the beginning of Chapter 2 “Soiving the Problem” to 2.2 JP 2002-99404 A JP-A-7-107256

However, at the interface design stage, carriers are rarely able to confirm their specifications, so simply preparing an adapter did not shorten the development period until the start of network services.
In addition, even if the network management device interface specifications are combined with the new function of the network element, actually, a confirmation test of the actual machine interface with respect to the network element after the release of command responses, protocols, and the like is required. For this reason, depending on the confirmation test, it was necessary to redo the development from interface design to adapter coding of the network management device after the test.

  In addition, after the network service is started, it is necessary to update the network element operating system and change the network configuration by adding functions and bug fixes, and network elements and interfaces are frequently updated. Cannot connect to network management device or server group. In this case as well, after the network element is released, the actual device test is performed to confirm the interface specifications, and then the connection test with the network management device in operation is performed. .

In particular, when an interface of a network element to be newly introduced does not correspond to a network management apparatus in operation, it is necessary to design an adapter specification corresponding to the network element and code a new adapter.
SUMMARY OF THE INVENTION Accordingly, an object of the present invention is to generate a script that conforms to the interface specification of a newly installed connection destination communication device, thereby making it possible to improve the efficiency of the verification test of the interface specification of the connection destination communication device A generation device, a script generation method, and a script generation program are provided.

In order to solve the above-described problem, according to the script generation device of claim 1, the one device can be an interactive application that advances processing while repeating command transmission and response reception with the connection destination communication device. It used, and scripts collecting means for collecting the process to be executed contents are written script according to the contents of the instruction and the response from the script collected by said script collection means, the predefined keywords A summary attribute extracting means for extracting as a summary attribute representing characteristics of the command content or the response content, and a script adapted to the interface specification of the already-connected connection destination communication device extracted by the summary attribute extracting means. by rearranging the summary attribute for the interface specification of the destination communication device to be introduced into the new The script candidates are reconfigured, and among the script candidates, the script candidates that actually conform to the interface specifications of the newly introduced connection destination communication device are adapted to the interface specifications of the newly introduced connection destination communication device. Script reconstructing means employed as a script to be used.

  As a result, various scripts can be reconfigured while making it possible to divert the existing scripts. For this reason, even if a difference in script description is found, it is possible to obtain a script that returns the expected response by repeating the trial, and a script that conforms to the interface specifications of the newly installed connection destination communication device. Automatic generation is possible. As a result, it is possible to reduce the trouble of performing the interface specification confirmation test while trying the command manually, and to improve the efficiency of the interface specification confirmation test of the connection destination communication device.

According to the script generation device of claim 2, the summary attribute extraction unit decomposes the script into a setting description part, a connection description part, and an instruction description part based on the decomposition knowledge definition, and the connection description Part and the instruction description part are defined by a predefined character string condition and set as a unit of processing in the connection description part and the instruction description part as one dialog, the connection description part and wherein the script decomposing means for dividing the command description section on the interactive unit, and a keyword extraction means for extracting the keyword any is included in at least one of the connection description part and the instruction description unit to the dialogue unit, the script reconstruction means is, this rearranging the keywords extracted by the keyword extraction means with the dialogue unit Accordingly, characterized in that it comprises a conversion dialog description generating means for generating a different conversion dialog description from the description of the interaction of the pre-recombinant.

  As a result, it is possible to rearrange the keywords in units of dialogs, and it is possible to prevent unnatural rearrangement that does not establish a dialog. For this reason, even if a difference in script description is found, it is possible to obtain a script that returns the expected response by repeating the trial, and a script that conforms to the interface specifications of the newly installed connection destination communication device. Automatic generation is possible.

According to the script generation device of claim 3, the NE command file that defines the conversion rule of the keyword, and a vocabulary in which synonyms and antonyms of the vocabulary of the command character string composed of the keyword are stored. further comprising at least one of the conversion rule database, the script reconstruction means, that the NE command file based on any one of at least one of the reference results of the lexical conversion rule database, to generate the converted dialog description It is characterized by.
This makes it possible to automatically generate a script that can extract the expected response even when a command with a similar description but a different description is used. The confirmation test can be made more efficient.

According to the script generation device of claim 4, by comparing the vocabulary and connection relationship between a plurality of processes for the same instruction with a process modeling means that abstractly represents the process representing the flow of the script, And a process integration means for integrating a plurality of processes.
Thereby, it is possible to reconstruct a script by combining a plurality of scripts having the same instruction. For this reason, even when a plurality of scripts having the same command are prepared corresponding to different connection destinations, it is possible to efficiently obtain a script that returns an expected response.

Further, according to the script generating apparatus according to claim 5, wherein the process modeling means, and class generating means for generating the extracted dialog description into the dialogue unit as a class, the class name keywords extracted from the dialog description and a class name assigning means for assigning to the class as, the process integration unit by integrating a plurality of processes, includes a class integrating means to integrate the classes to each other included in each process, the conversion dialog description generating means, by rearranging the keyword class integrated by the class integrating unit on a class-by-class basis, and generates the converted dialog description.

  As a result, even when multiple scripts are combined, it is possible to reconfigure the scripts while preventing unnatural recombination that does not establish a conversation, and the same for different connection destinations. Even when a plurality of instruction scripts are prepared, it is possible to efficiently obtain a script that returns an expected response.

Further, according to the script generation method of claim 6 , the command and the command are used for an interactive application in which one device advances processing while repeating command transmission and response reception with a connection destination communication device. A step of collecting a script in which processing content to be executed according to the content of the response is described; and a description of the collected script, which is defined by a predefined character string condition and is a unit of processing in the script the set comprising in part as one of the dialogue, and decomposing the description of the script to the dialogue unit, the predefined keywords included in the script, in the dialogue unit as an overview attributes representing features of the interaction extracting, subscriptions that have already been adapted to the interface specification of the destination communication apparatus has been introduced By rearranging the summary attribute of bets, reconfigure the script candidate for interface specification of the destination communication device to be introduced into a new, among the scripts candidate, the interface specification of the destination communication device to be introduced into the new And adopting a script candidate that actually conforms to a script that conforms to the interface specification of the newly introduced connection destination communication device .

  As a result, it is possible to confirm the consistency of whether the script description can be diverted, and when a difference in the script description is found, it is possible to reconstruct a script that returns an expected response by repeating the trial. For this reason, it is possible to automatically generate a script that conforms to the interface specification of the newly connected destination communication device, and to improve the efficiency of the confirmation test of the interface specification of the connection destination communication device. As a result, the design and development process of the system used for the network service can be shortened, and even when a network element with a new function is frequently added or renewed, the network service in which the network element is introduced Can be started early.

Further, according to the script generation method according to claim 7, wherein the step of decomposing the description of the script to the dialogue unit is based on the decomposition knowledge definition, set the scripting part, the connection description part and instruction description unit on decomposed, thereby degrading each defining the setting description section, and a decomposing the connection description part and the instruction description unit to the dialogue unit, the step of extracting the outline attribute in the dialogue unit , extracting extracting command strings from said decomposed into dialogue units connect descriptor unit or instruction description unit, by referring to the delimiter, the keyword decomposing the command string to the word unit And the step of reconfiguring the script differs by changing the order of the keywords in the dialog units. Characterized in that it comprises the steps of generating a story description.

  As a result, the keywords can be rearranged in units of dialog, and the script can be reconfigured while preserving the order of dialog. For this reason, even if a difference in script description is found, it is possible to obtain a script that returns the expected response by repeating the trial, and a script that conforms to the interface specifications of the newly installed connection destination communication device. Automatic generation is possible.

In addition, according to the script generation method of claim 8, a step of generating a class expressing the dialog description decomposed in units of dialogs in an abstract manner, and adding a keyword included in the class as a class name of the class A step of abstracting and expressing a connection relationship of processes representing a flow of a script by determining a connection relationship including an execution order or branching between the dialog descriptions, and a vocabulary between a plurality of processes for the same instruction And integrating the plurality of processes into one process by comparing the connection relation, and assigning the class names of the plurality of classes before integration as class names of the classes constituting the integrated process; By switching the order of the keywords in the integrated class unit, Generating a description.
As a result, even when multiple scripts are combined, it is possible to reconfigure the scripts while preserving the order of dialogue, and when multiple scripts with the same command are prepared corresponding to different connection destinations. However, it is possible to efficiently obtain a script that returns an expected response.

In addition, according to the script generation program of claim 9 , the command and the command that are used for an interactive application in which one device advances processing while repeating command transmission and response reception with a connection destination communication device. A step of collecting a script in which processing content to be executed according to the content of the response is described; and a description of the collected script, which is defined by a predefined character string condition and is a unit of processing in the script the set comprising in part as one of the dialogue, and decomposing the description of the script to the dialogue unit, the predefined keywords included in the script, in the dialogue unit as an overview attributes representing features of the interaction extracting, already adapted to the interface specification of the destination communication apparatus has been introduced By rearranging the summary attribute Crypto reconstructs script candidate for interface specification of the destination communication device to be introduced into a new, among the scripts candidate, the interface specification of the destination communication device to be introduced into the new And a step of adopting a script candidate that actually conforms to a script that conforms to the interface specification of the newly introduced connection destination communication apparatus .
As a result, by executing the script generation program on the computer, a script that conforms to the interface specifications of the newly installed connection destination communication device can be automatically generated, and the interface specification confirmation test of the connection destination communication device can be efficiently performed. Can be realized.

According to the script generation program of claim 10 , the command and the command are used for an interactive application in which one device advances processing while repeating command transmission and response reception with a connection destination communication device. A step of collecting a script in which processing content to be executed according to the content of the response is described; and a description of the collected script, which is defined by a predefined character string condition and is a unit of processing in the script The step of setting the set part as one dialog , decomposing the description of the script into the dialog units, and a summary attribute representing the characteristics of the dialog from a keyword defined in advance from the script decomposed into the dialog units extracting as a class that represents abstracts dialog description that is decomposed into the dialogue unit A step of forming, a step of constructing a process model representing a connection relationship of a process representing the flow of the script, while preserving the order relation dialog description of each script, a process model of the plurality of script for each instruction type a step of integrating, on the basis of the summary attribute of the pre-integration class, conforming to the interface specifications of the integrated extracting class Summary attributes of the process model, already connected communication apparatus which has been introduced script of by rearranging the summary attribute, reconfigure the script candidate for interface specification of the destination communication device to be introduced into a new, among the scripts candidate, the interface specification of the destination communication device to be introduced into the new The newly adapted script candidates are newly introduced. Characterized in that and a step of employing as compatible script interface specification of the connected communication device to the computer.

  As a result, by causing the computer to execute the script generation program, even when a plurality of instruction scripts having the same purpose corresponding to different connection destinations are prepared, the newly introduced connection destination communication device A script conforming to the interface specification can be automatically generated, and the confirmation test of the interface specification of the connection destination communication device can be made efficient.

  As described above, according to the present invention, it is possible to automatically generate a script that conforms to the interface specification of a newly installed connection destination communication device, and to improve the efficiency of the confirmation test of the interface specification of the connection destination communication device. can do. As a result, the design and development process of the system used for the network service can be shortened, and even when a network element with a new function is frequently added or renewed, the network service in which the network element is introduced Can be started early.

Hereinafter, a script generation device and an interface test method according to an embodiment of the present invention will be described with reference to the drawings.
FIG. 1 is a block diagram illustrating a schematic configuration example of an NE interface test apparatus using an interactive application according to an embodiment of the present invention.
In FIG. 1, the service providing network 3 and the test network 4 are provided with network elements 3a and 4a, respectively. Examples of the network elements 3a and 4a include a router having a telnet interactive interface function.

  Further, the network management apparatus 2 is provided with an NE interface 22 that is responsible for an interface function with the network element 3a by an interactive application, and holds a script 21 used by the NE interface 22. The network management device 2 is connected to the service providing network 3 via the NE interface 22.

  Further, the interface test apparatus 1 includes an IF input unit 101 that inputs a script 21, an IF description decomposition unit 102 that decomposes the script 21 into dialog units, a decomposition knowledge definition 103 that defines knowledge for disassembling the script 21, a script IF description modeling unit 104 that generates a conversion dialog description having different dialog attributes based on the keywords extracted from 21, an IF description database 105 that stores the conversion dialog description generated by the IF description modeling unit 104, and vendor-specific commands Vendor knowledge definition unit 106 that holds a system, NE command file 107 that defines conversion rules for keywords, vocabulary conversion rule database 108 that stores lexical synonyms and antonyms of command character strings, and IF description modeling unit 104 Use the generated conversion dialog description. Test IF described preparation unit 109 to reconstruct, IF palpation unit 110 for confirmation test of actual interface to the network element 4a of the test network 4 is provided a script 21 by.

  The IF description decomposing unit 102 decomposes the script 21 into a setting description unit, a connection description unit, and an instruction description unit, then decomposes the setting description unit for each definition, and converts the connection description unit and the instruction description unit into dialog units. Can be broken down into Further, the IF description modeling unit 104 extracts a keyword included in the connection description unit or the command description unit in a dialog unit, and generates a converted dialog description having different dialog attributes by rearranging the extracted keyword in the dialog unit. Can do. Also, in the IF description database 105, a setting description part table 105a, a connection description part table 105b, and an instruction description for storing attributes of the setting description part, the connection description part, and the instruction description part that are decomposed by the IF description decomposition part 102, respectively. A section table 105c is provided.

Hereinafter, a method of generating test IF information by inputting one script 21 to the interface test apparatus 1 will be described.
FIG. 2 is a sequence diagram showing a procedure from script input to storing test IF information in the interface test apparatus 1 of FIG.
In FIG. 2, the network management apparatus 2 can connect to the service providing network 3 by an interactive application such as telnet by using the NE interface 22. Further, the network management device 2 corresponds to an interface unique to each vendor as an interactive description, and can achieve an object such as information collection of the service providing network 3 by connecting to the network element 4a. Has multiple script files.
Then, one of the scripts 21 held in the network management device 2 is input to the IF input unit 101 via the terminal 5 (S1, S2).

FIG. 3 is a diagram showing a description example and a decomposition unit of the script 21 of the interactive application according to the embodiment of the present invention.
In FIG. 3, the script 21 includes a setting description part B1, a connection description part B2, and a command description part B3. Here, in the setting description part B1, initial values set before the start of communication by the interactive application are described. In addition, the connection description part B2 describes routine exchanges such as login and password setting required when the interactive application starts communication. The connection description part B2 is configured with the conversations W1 and W2 as units. ing. In addition, the command description part B3 describes the exchange of commands that achieve the purpose by communication, and the command description part B3 is configured in units of dialogs W3 to W5. An information collection procedure can be automated by previously describing a command that is originally input manually and a command for the response.

Here, when the script 21 is input from the terminal 5 to the IF input unit 101, the product name of the network element 4a targeted by the script 21 and the purpose outline (purpose name) of the script 21 can be input. For example, as shown below, a script file can be read by inputting a file name from CLI (Command Line Interface), and the NE product name and the target name of the script 21 can be input in a text format.
input <file name (example: getIpv6info.txt)><NE product name (example: JuniperM5)>: <target name (example: GetIPv6MldInfo)>

  When the NE product name and the purpose name of the script 21 are input, the IF input unit 101 creates a directory indicating the NE product name at an arbitrary location of the interface test apparatus 1 using the NE product name (for example, Juniper M5). . Then change the file name to the target name and save the script file in that directory.

  If a directory already exists in the interface test apparatus 1, the file name is changed to the target name, and the script file is saved in the directory. When a directory already exists in the interface test apparatus 1 and an input having the same value as the NE product name and the target name exists in the past, a warning that a script file with the same target name already exists is displayed on the CLI and the file is also displayed. The name is displayed on the terminal 5 and asked whether to overwrite the script file.

And when a user chooses not to overwrite through the terminal 5, a process is complete | finished. On the other hand, when the user selects to overwrite through the terminal 5, the existing script file is replaced.
When the script file is overwritten, or when the script file with the same NE product name and target name does not exist and the script file is saved in the directory, the IF input unit 101 converts the NE product name and target name into the IF description decomposition unit. (S3).

  When receiving the NE product name and the target name from the IF input unit 101, the IF description decomposing unit 102 searches the directory having the same name as the NE product name, and searches the directory for the script file having the same name as the target name. . If there is no script file having the same name as the target name received from the IF input unit 101, the process is terminated. On the other hand, if a script file having the same name as the target name received from the IF input unit 101 exists, the IF description decomposition unit 102 sets the script 21 included in the script file according to the description of the decomposition knowledge definition 103 (S4, S5). It is broken down into a description part B1, a connection description part B2 and an instruction description part B3 (S6). Further, the IF description decomposition unit 102 separately extracts a command to be actually communicated from the script 21. Further, the IF description decomposing unit 102 decomposes the connection description unit B2 and the instruction description unit B3 for each of the dialogs W1 to W5 as shown in FIG. 3 (S6).

FIG. 4 is a diagram showing a description example of the decomposition knowledge definition 103 in the interactive application according to the embodiment of the present invention. The decomposed knowledge definition 103 can be described in a text format and can be edited by the terminal 5.
In FIG. 4, a setting description part B1 is defined by “def pri”, a connection description part B2 is defined by “def conn_start”, and an instruction description part B3 is defined by “def conv_start” and “def conv_end”. Further, dialogues W1 to W5 are defined by “def conv_end”. Further, a keyword for extracting features of the dialogs W1 to W5 is defined by “def key”.

Here, the interface test apparatus 1 can hold a plurality of setting files describing the disassembly knowledge definition 103. As for which decomposition knowledge definition 103 the IF description decomposition unit 102 uses, there is a method of determining a default in advance by describing a file name in a setting file. Further, as shown below, when inputting the file name, the target name, and the NE product name of the script 21 from the CLI, the file name of the disassembly knowledge definition 103 may be input.
input <file name (example: getIpv6Mldinfo.txt)><NE product name (example: JuniperM5)>: <target name (example: GetIPv6Info)>-knowledge <file name of decomposition knowledge definition 103 (example: forExpectKn.txt)>

  Then, when decomposing the script 21, the IF description decomposing unit 102 confirms the character string after “def pri” described in the decomposed knowledge definition 103. In the decomposed knowledge definition 103 of FIG. 3, “def pri” is described from the fourth line to the seventh line, and the characters “#!”, “Set”, “log user”, and “append” are written after “def pri”. Each column is described. For this reason, the IF description decomposition unit 102 regards a line beginning with the character string “#!”, “Set”, “log user”, or “append” as the setting description unit B1. For example, in the script 21 of FIG. 3, “#! / Usr / local / bin / expect”, a line beginning with “set”, and a line beginning with “append” are regarded as the setting description part B1.

  And IF description decomposition | disassembly part 102 will extract the substitution relation of a character from setting description part B1, if setting description part B1 is extracted from the script 21. FIG. For example, in the script 21 in FIG. 3, “5” is assigned to “timeout” on the fourth line. Then, the non-substitution character is replaced with the substitution character for the part other than the setting description portion B1. For example, in the script 21 of FIG. 3, the character string “$ command” in the 27th is replaced with “show ipv6 mld”. Here, even when the connection description part B2 and the instruction description part B3 are separated from the setting description part B1 by replacing the non-assignment character with the substitution character for a part other than the setting description part B1, the setting description part The contents set in B1 can be given to the connection description part B2 and the instruction description part B3.

FIG. 5 is a diagram showing a description example of the connection description part B2 and the instruction description part B3 after substitution character substitution of the interactive application according to the embodiment of the present invention.
In FIG. 5, the connection description part B2 and the instruction description part B3 are separated from the setting description part B1, and the substitution character set in the setting description part B1 is replaced with a non-substitution character.

  Then, when the IF description decomposition unit 102 replaces the non-substitution character in the part other than the setting description unit B1 with the substitution character, the character string after “def conv_start” described in the decomposition knowledge definition 103 and after “def conv_end” Check the string. Then, the instruction description portion B3 is determined from the line where the character string after “def conv_start” first appears to the line where the character string after “def conv_end” first appears. For example, in the disassembled knowledge definition 103 in FIG. 3, a character string “send” is described after “def conv_start”, and a character string “close” is described after “def conv_end”. Therefore, the IF description decomposing unit 102 determines the instruction description unit B3 from the line where the character string “send” first appears to the line where the character string “close” first appears. For example, in the script 21 of FIG. 3, the character string “send” first appears on the 22nd line, and the character string “close” appears first on the 35th line. The instructions up to the eyes are regarded as the instruction description part B3.

  Next, when the instruction description part B 3 is extracted from the script 21, the IF description decomposition part 102 checks the character string after “def conn_start” described in the decomposition knowledge definition 103. Then, in the parts not extracted as the setting description part B1 and the instruction description part B3, the connection description part B2 extends from the line where the character string after “def conn_start” first appears to the one line before the instruction description part B3. Judge. For example, in the disassembled knowledge definition 103 in FIG. 3, a character string “spun” is described after “def conn_start”. For this reason, the IF description decomposing unit 102 is one line before the instruction description unit B3 from the line where the character string “spun” first appears in the part not extracted as the setting description unit B1 and the instruction description unit B3. Are determined to be the connection description part B2. For example, in the script 21 of FIG. 3, since the character string “spun” first appears on the 11th line, the 11th to 21st lines are regarded as the connection description part B2.

  Next, when the script description 21 is decomposed into the setting description part B1, the connection description part B2, and the instruction description part B3, the IF description decomposition part 102 decomposes the connection description part B2 and the instruction description part B3 into dialog units. Specifically, the IF description decomposition unit 102 checks the character string condition after “def conv_end” described in the decomposition knowledge definition 103. And the part prescribed | regulated by the character string condition after "def conv_end" is judged as dialog W1-W5. For example, in the decomposed knowledge definition 103 in FIG. 3, after “def conv_end”, character strings “expect {” and “}”, “spawn * expect {” and “}”, “send * expect {”, and “}” are included. Each is described. Note that * is a regular expression representing an arbitrary character string. For this reason, the IF description decomposition unit 102 includes a portion surrounded by “expect {” and “}”, a portion surrounded by “spawn * expect {” and “}”, and “send * expect {” and “}”. The portions surrounded by are determined as dialogues W1 to W5, respectively. For example, in the script 21 of FIG. 3, the connection description part B2 is decomposed into dialogs W1 and W2, and the instruction description part B3 is decomposed into dialogs W3 to W5.

  Then, the IF description decomposition unit 102 decomposes the script 21 into the setting description unit B1, the connection description unit B2, and the command description unit B3, and then decomposes the connection description unit B2 and the command description unit B3 into dialogs W1 to W5. Unique ID information for each NE product name, purpose name, and script 21 sent from the IF input unit 101 is given to the setting description unit B1, the connection description unit B2, and the command description unit B3, respectively, and the setting description unit table 105a, connection It stores in the description part table 105b and the instruction description part table 105c, respectively. At this time, the connection description part B2 and the instruction description part B3 store each dialog W1-W5 in one table. Also, storage is performed in order from the dialogue described in the upper part, and a unique object No. Is granted. In addition, the previous object number assigned to each of the previous and subsequent dialogs is displayed. The post-object number is also stored in the connection description part table 105b and the instruction description part table 105c, respectively. When a dialog is searched, the dialog before and after the dialog can be searched.

6 is a diagram showing an example of the setting description part table 105a, the connection description part table 105b, and the instruction description part table 105c stored in the IF description database 105 of FIG. ID information uniquely assigned to each script 21, NE product name for determining the type of the network element 3 a, purpose name indicating the purpose of the script 21 used by the network management device 2, and decomposed setting description part B 1 A description is stored.

  In the connection description part table 105b, ID information uniquely assigned to each script 21, the NE product name for determining the type of the network element 3a, and the purpose of the script 21 used by the network management device 2 are shown. Name, the dialog description of the connection description part B2, the keyword indicating the characteristics of the dialog description, and the object number uniquely assigned to each dialog. The previous object number assigned to each of the previous and next dialogs. And the rear object No. Is stored. Also, a conversion dialog description in which the dialog description command is changed is stored.

  The command description part table 105c also includes ID information uniquely assigned to each script 21, the NE product name for determining the type of the network element 3a, and the purpose of the script 21 used by the network management device 2. Name, the dialog description of the decomposed instruction description part B3, a keyword representing the characteristics of the dialog description, and the object number uniquely assigned to each dialog. The previous object number assigned to each of the previous and next dialogs. And the rear object No. Is stored. Also, a conversion dialog description in which the dialog description command is changed is stored.

The IF description decomposing unit 102 stores the instruction description unit table when the setting description unit B1, the connection description unit B2, and the instruction description unit B3 are stored in the setting description unit table 105a, the connection description unit table 105b, and the instruction description unit table 105c, respectively. The IF description modeling unit 104 is notified of the ID assigned to the file stored in 105c (S7).
When receiving the ID from the IF description decomposing unit 102, the IF description modeling unit 104 searches the IF description database 105 for all the dialog attributes of the instruction description unit B3 using the ID as key information (S8, S9). When the IF description modeling unit 104 retrieves the dialog attribute of the command description unit B3, the IF description modeling unit 104 extracts a keyword representing the feature of the dialog description from each dialog attribute of the command description unit B3, and uses the IF description database 105 as a summary attribute of the dialog description. Is stored for each dialog (S10).

  Here, in order to extract a keyword from each dialogue attribute of the instruction description part B3, the IF description modeling part 104 uses reserved characters such as “expect”, {(parentheses),. Delimiters such as (period) can be held as knowledge. A character string other than the corresponding character can be separated as a special character by a space character, and the separated word can be treated as a keyword. Further, in order to extract a keyword, for example, in the case of interaction information including an instruction, the interaction information not including an instruction is extracted so that a command character string (“show ipv6 route” in the example of FIG. 5) is extracted. In this case, the reserved character can be registered so that the character string actually transmitted from the interactive interface is extracted as the outline information by “send”. In this case, the IF description modeling unit 104 can also perform processing such as describing “send” in the decomposed knowledge definition 103 and extracting the character after “send” as a keyword (S11, S12).

FIG. 7 is a diagram illustrating an example of a keyword extraction method by the IF description modeling unit 104 of FIG.
7, in the instruction description part B3 of FIG. 3, the words “terminal”, “pager”, and “off” are extracted as keywords from the dialogue W3, and the keywords “show” and “ipv6” are extracted from the dialogue W4. ”And“ mld ”are extracted, and the word“ exit ”is extracted as a keyword from the dialogue W5.

  And IF description modeling part 104 will extract a keyword from dialog W3-W5 of command description part B3, and will store a keyword in command description part table 105c in order from the dialog described above. Then, the IF description modeling unit 104 abstracts the dialog description extracted for each dialog unit, stores it as a class in the command description unit table 105c, and assigns a keyword as the class name of the class, thereby causing the flow of the script 21 to flow. A process model expressing the connection relationship of the process to be expressed can be constructed (S14 to S17).

FIG. 8 is a diagram showing an example of a script process modeling method by the IF description modeling unit 104 of FIG.
In FIG. 8, the keywords “terminal”, “pager”, and “off” are extracted from the dialogue W3, the keywords “show”, “ipv6”, and “mld” are extracted from the dialogue W4, and the keyword “exit” is When extracted from the dialogue W5, the classes corresponding to the dialogues W3 to W5 are connected in the order of the dialogues W3 to W5 between the “process start” and the “process end”, and extracted from the dialogues W3 to W5. By assigning a keyword to each class as a class name, it is possible to construct a process model in which the order and characteristics of each of the dialogs W3 to W5 of the instruction description unit B3 are expressed by keywords.

  Further, the IF description modeling unit 104 searches the IF description database 105 for the setting description unit B1 using the ID as key information, and notifies the vendor knowledge definition unit 106 of the setting description unit B1 (S13). Here, the vendor knowledge definition unit 106 is provided with a product name directory for separately storing the setting description unit B1. When the vendor knowledge definition unit 106 receives the setting description unit B1 from the IF description modeling unit 104, the vendor knowledge definition unit 106 stores the setting description unit B1 in the product name directory with the target name as the file name.

  Further, the IF description modeling unit 104 notifies the test IF description blending unit 109 of the ID (S18). When receiving the ID from the IF description modeling unit 104, the test IF description blending unit 109 searches the IF description database 105 for the dialog attribute and the summary attribute of the command description unit B3 using the ID as key information. Then, when searching for the summary attribute of the instruction description unit B3 from the IF description database 105, the test IF description preparation unit 109 generates a plurality of command character strings by rearranging the keywords constituting the summary attribute. Then, the conversion dialogue description is generated by exchanging the command character string of the dialogue attribute, and is stored in the command description portion table 105c (S22). For example, since the keywords “show”, “ipv6”, and “mld” are extracted from the dialogue W4 in the instruction description part B3 in FIG. 3, “show mld”, “show ipv6” are rearranged by reassigning these keywords. ”,“ Show mld ipv6 ”, and the like can be generated.

  Further, the IF description modeling unit 104 searches the NE command file 107 by keyword. If the conversion rule for the keyword is defined in the NE command file 107, the conversion dialog description is generated by converting the keyword in the dialog description, and is stored in the command description part table 105c (S22).

FIG. 9 is a diagram illustrating a description example of the NE command file 107 in FIG. 1. In FIG. 9, for example, the commands “show pim join extensible” and “show ipv6 mroute” are used as conversion rules for “show mld ipv6”. Assuming that a character string is defined, a conversion dialog description can be generated by replacing the command character string “show mld ipv6” with a command character string “show pim join extensible” or “show ipv6 mroute”. .
Further, the IF description modeling unit 104 searches the vocabulary conversion rule database 108 using keywords. When a synonym phrase or an antonym phrase of the vocabulary of the command character string is defined in the vocabulary conversion rule database 108, a conversion dialog description is generated by converting the command character string in the dialog description, and an instruction description section table It is stored in 105c (S22).

FIG. 10 is a diagram showing an example of the contents of the lexical conversion rule database 108 of FIG. 1. In FIG. 10, for example, “show ip mld”, “show ipv4 mroute” are used as synonyms or antonyms of “show mld ipv6”. ”,“ Show ipv4 route ”, and“ show ipv6 multicast ”command strings are defined,“ show ip mld ”,“ show ipv4 route ”,“ show ipv4 route ”or“ show iptic 6 ” A conversion dialogue description in which the command character string “show mld ipv6” is replaced with the command character string can be generated.

  In this way, a plurality of dialogue attributes in which commands are changed according to keyword rearrangement of the command character string and the NE command file 107 or the lexical conversion rule database 108 are generated. These dialog attributes are stored in the IF description database 105 as attribute information in the same table as the original as a dialog description revised for the original dialog description.

FIG. 11 is a sequence diagram showing a procedure from the terminal 5 of FIG. 1 to input to each database and knowledge definition.
In FIG. 11, the disassembled knowledge definition 103 can be edited by accessing the interface test apparatus 1 from the terminal 5 (S31). The NE command file 107 and the lexical conversion rule database 108 can also be edited by the terminal 5 (S32, S33).

  Then, the IF palpation unit 110 implements a connection method similar to the NE interface 22 by the above-described method, and actually uses the test IF description file in which a plurality of dialog descriptions whose instructions are changed is combined on the test network 4. By performing the test, it is possible to perform a confirmation test of the IF specification using an instruction in which an instruction and an instruction character string existing in an existing IF description file are automatically rearranged.

  For this reason, it is possible to reduce time and effort required for manually trying the command and performing a confirmation test of the actual IF specification. In addition, by generating a command in which the command character string is rearranged, it is possible to increase the possibility that a response can be drawn to the network elements 3a and 4a that require the same command but a different description. At this time, by adding a vendor-specific command system to the IF description, it is possible to improve the accuracy of IF analysis when the operating system of the network elements 3a and 4a is updated.

FIG. 12 is a sequence diagram showing a procedure of a palpation test for a test network using the test IF description generated by the interface test apparatus of FIG.
In FIG. 12, when performing a palpation test on the test network 4 using the test IF description, the interface 5 is accessed from the terminal 5 to give a test instruction to the IF palpation unit 110 and the script 21. A target name is input (S41). When the IF palpation unit 110 receives the purpose name of the script 21, it sends the purpose name to the test IF description composition unit 109. Then, when receiving the purpose name of the script 21 from the IF palpation unit 110, the test IF description preparation unit 109 searches the IF description database 105 and the vendor knowledge definition unit 106 using the purpose name as key information (S43, S45). ), An instruction description portion and a setting description portion corresponding to the purpose name are acquired (S44, S46). When the test IF description blending unit 109 acquires the instruction description part and the setting description part corresponding to the purpose name of the script 21, the test IF description preparation part 109 generates a test script using the instruction description part and the setting description part. This is sent to the palpation unit 110 (S47).

  When the IF palpation unit 110 receives the test script from the test IF description blending unit 109, the IF palpation unit 110 performs a palpation test on the test network 4 (S48). And if the IF palpation part 110 draws out the response from the network element 4a as a result of a palpation test (S49), it will transmit a test content and a response to the terminal 5 (S50).

  This makes it possible to automate NE-IF analysis tests of actual machines and automatically generate NMS (Network Management System) -IF adapters, enabling NMS to be introduced and renewed in a short period of time, and by automating IF description processing. The burden of NE analysis and NMS-IF development for new NEs by NMS developers can be reduced. For this reason, it is possible to reduce the time and effort required to test the NE-IF and the development process of the NMS-IF adapter, and it is possible to shorten the design and development process of the system that constitutes the service. The service can be started as early as possible even in the current situation where the specifications of the IF are frequently changed as the life cycle of the network service using the network becomes shorter.

  Next, a method for generating test IF information by combining a plurality of scripts 21 will be described. Here, when a plurality of scripts 21 are used, after the first script 21 is stored as test IF information according to the procedure for inputting one script 21 described above, another script 21 is added to the test IF information. Combine. By repeating this method, test IF information combining a plurality of scripts 21 can be generated.

Then, one of the scripts 21 held in the network management device 2 is input to the IF input unit 101 via the terminal 5.
Here, when the script 21 is input from the terminal 5 to the IF input unit 101, the product name of the network element 4a targeted by the script 21 and the purpose name of the script 21 can be input. For example, the script file can be read by inputting a file name from the CLI, and the NE product name and the target name of the script 21 can be input in a text format.

When the NE product name and the purpose name of the script 21 are input, the IF input unit 101 creates a directory in an arbitrary location of the interface test apparatus 1 using the NE product name (for example, Cisco 7206). Then change the file name to the target name and save the script file in that directory.
If a directory already exists in the interface test apparatus 1, the file name is changed to the target name, and the script file is saved in the directory. When a directory already exists in the interface test apparatus 1 and an input having the same value as the NE product name and the target name exists in the past, a warning that a script file with the same target name already exists is displayed on the CLI and the file is also displayed. The name is displayed on the terminal 5 and asked whether to overwrite the script file.

And when a user chooses not to overwrite through the terminal 5, a process is complete | finished. On the other hand, when the user selects to overwrite through the terminal 5, the existing script file is replaced.
When the script file is overwritten, or when the script file with the same NE product name and target name does not exist and the script file is saved in the directory, the IF input unit 101 converts the NE product name and target name into the IF description decomposition unit. 102.

  When receiving the NE product name and the target name from the IF input unit 101, the IF description decomposing unit 102 searches the directory having the same name as the NE product name, and searches the directory for the script file having the same name as the target name. . If there is no script file having the same name as the target name received from the IF input unit 101, the process is terminated. On the other hand, if there is a script file having the same name as the target name received from the IF input unit 101, the IF description decomposition unit 102 connects the script 21 included in the script file to the setting description unit B1, according to the description of the decomposition knowledge definition 103. It is broken down into a description part B2 and an instruction description part B3. Further, the IF description decomposition unit 102 separately extracts a command to be actually communicated from the script 21. Further, the IF description decomposition unit 102 decomposes the connection description unit B2 and the instruction description unit B3 for each of the dialogs W1 to W5 as shown in FIG. The decomposed knowledge definition 103 can be described in a text format and can be edited by the terminal 5.

  Here, the interface test apparatus 1 can hold a plurality of setting files describing the disassembly knowledge definition 103. As for which decomposition knowledge definition 103 the IF description decomposition unit 102 uses, there is a method of determining a default in advance by describing a file name in a setting file. Further, when inputting the file name, the target name, and the NE product name of the script 21 from the CLI, the file name of the decomposition knowledge definition 103 may be input.

  Then, when decomposing the script 21, the IF description decomposing unit 102 confirms the character string after “def pri” described in the decomposed knowledge definition 103. In the decomposed knowledge definition 103 of FIG. 3, “def pri” is described from the fourth line to the seventh line, and the characters “#!”, “Set”, “log user”, and “append” are written after “def pri”. Each column is described. For this reason, the IF description decomposition unit 102 regards a line beginning with the character string “#!”, “Set”, “log user”, or “append” as the setting description unit B1. For example, in the script 21 of FIG. 3, “#! / Usr / local / bin / expect”, a line beginning with “set”, and a line beginning with “append” are regarded as the setting description part B1.

  And IF description decomposition | disassembly part 102 will extract the substitution relation of a character from setting description part B1, if setting description part B1 is extracted from the script 21. FIG. For example, in the script 21 in FIG. 3, “5” is assigned to “timeout” on the fourth line. Then, the non-substitution character is replaced with the substitution character for the part other than the setting description portion B1. For example, in the script 21 of FIG. 3, the character string “$ command” on the 28th line is replaced with “show ipv6 mld”.

  Then, when the IF description decomposition unit 102 replaces the non-substitution character in the part other than the setting description unit B1 with the substitution character, the character string after “def conv_start” described in the decomposition knowledge definition 103 and after “def conv_end” Check the string. Then, the instruction description portion B3 is determined from the line where the character string after “def conv_start” first appears to the line where the character string after “def conv_end” first appears. For example, in the disassembled knowledge definition 103 in FIG. 3, a character string “send” is described after “def conv_start”, and a character string “close” is described after “def conv_end”. Therefore, the IF description decomposing unit 102 determines the instruction description unit B3 from the line where the character string “send” first appears to the line where the character string “close” first appears. For example, in the script 21 of FIG. 3, the character string “send” first appears on the 22nd line, and the character string “close” appears first on the 35th line. The instructions up to the eyes are regarded as the instruction description part B3.

  Next, when the instruction description part B 3 is extracted from the script 21, the IF description decomposition part 102 checks the character string after “def conn_start” described in the decomposition knowledge definition 103. Then, in the parts not extracted as the setting description part B1 and the instruction description part B3, the connection description part B2 extends from the line where the character string after “def conn_start” first appears to the one line before the instruction description part B3. Judge. For example, in the disassembled knowledge definition 103 in FIG. 3, a character string “spun” is described after “def conn_start”. For this reason, the IF description decomposing unit 102 is one line before the instruction description unit B3 from the line where the character string “spun” first appears in the part not extracted as the setting description unit B1 and the instruction description unit B3. Are determined to be the connection description part B2. For example, in the script 21 of FIG. 3, since the character string “spun” first appears on the 11th line, the 11th to 21st lines are regarded as the connection description part B2.

  Next, when the script description 21 is decomposed into the setting description part B1, the connection description part B2, and the instruction description part B3, the IF description decomposition part 102 decomposes the connection description part B2 and the instruction description part B3 into dialog units. Specifically, the IF description decomposition unit 102 checks the character string condition after “def conv_end” described in the decomposition knowledge definition 103. And the part prescribed | regulated by the character string condition after "def conv_end" is judged as dialog W1-W5. For example, in the decomposed knowledge definition 103 in FIG. 3, after “def conv_end”, character strings “expect {” and “}”, “spawn * expect {” and “}”, “send * expect {”, and “}” are included. Each is described. Note that * is a regular expression representing an arbitrary character string. For this reason, the IF description decomposition unit 102 includes a portion surrounded by “expect {” and “}”, a portion surrounded by “spawn * expect {” and “}”, and “send * expect {” and “}”. The portions surrounded by are determined as dialogues W1 to W5, respectively. For example, in the script 21 of FIG. 3, the connection description part B2 is decomposed into dialogs W1 and W2, and the instruction description part B3 is decomposed into dialogs W3 to W5.

  Then, the IF description decomposition unit 102 decomposes the script 21 into the setting description unit B1, the connection description unit B2, and the command description unit B3, and then decomposes the connection description unit B2 and the command description unit B3 into dialogs W1 to W5. Unique ID information for each NE product name, purpose name, and script 21 sent from the IF input unit 101 is given to the setting description unit B1, the connection description unit B2, and the command description unit B3, respectively, and the setting description unit table 105a, connection It stores in the description part table 105b and the instruction description part table 105c, respectively. At this time, the connection description part B2 and the instruction description part B3 store each dialog W1-W5 in one table. Also, storage is performed in order from the dialogue described in the upper part, and a unique object No. Is granted. In addition, the previous object number assigned to each of the previous and subsequent dialogs is displayed. The post-object number is also stored in the connection description part table 105b and the instruction description part table 105c, respectively. When a dialog is searched, the dialog before and after the dialog can be searched.

The IF description decomposing unit 102 stores the instruction description unit table when the setting description unit B1, the connection description unit B2, and the instruction description unit B3 are stored in the setting description unit table 105a, the connection description unit table 105b, and the instruction description unit table 105c, respectively. The IF description modeling unit 104 is notified of the ID assigned to the file stored in 105c.
When receiving the ID from the IF description decomposing unit 102, the IF description modeling unit 104 searches the IF description database 105 for all the dialog attributes of the instruction description unit B3 using the ID as key information. When the IF description modeling unit 104 retrieves the dialog attribute of the command description unit B3, the IF description modeling unit 104 extracts a keyword representing the feature of the dialog description from each dialog attribute of the command description unit B3, and uses the IF description database 105 as a summary attribute of the dialog description. Is stored for each dialog.

  Here, in order to extract a keyword from each dialogue attribute of the instruction description part B3, the IF description modeling part 104 uses reserved characters such as “expect”, {(parentheses),. Delimiters such as (period) can be held as knowledge. A character string other than the corresponding character can be separated as a special character by a space character, and the separated word can be treated as a keyword. Further, in order to extract a keyword, for example, in the case of interaction information including an instruction, the interaction information not including an instruction is extracted so that a command character string (“show ipv6 route” in the example of FIG. 5) is extracted. In this case, the reserved character can be registered so that the character string actually transmitted from the interactive interface is extracted as the outline information by “send”. In this case, the IF description modeling unit 104 can describe a process of describing “send” in the disassembled knowledge definition 103 and extracting a character after “send” as a keyword.

  The IF description modeling unit 104 searches the IF description database 105 for the setting description unit B1 using the ID as key information, and notifies the vendor knowledge definition unit 106 of the setting description unit B1. Here, the vendor knowledge definition unit 106 is provided with a product name directory for separately storing the setting description unit B1. When the vendor knowledge definition unit 106 receives the setting description unit B1 from the IF description modeling unit 104, the vendor knowledge definition unit 106 stores the setting description unit B1 in the product name directory with the target name as the file name.

  Here, the IF description modeling unit 104 searches the IF description database 105 using the ID and the purpose name as a key, and confirms whether there is an instruction description unit entry having the same target name but a different product name. If there is an entry in the instruction description part having the same object name but different product name, the existing description decomposed into IF description modeling generated from the network element of another product with the same instruction is combined.

13 to 15 are diagrams illustrating an example of a method for matching a plurality of modeled processes according to an embodiment of the present invention.
In FIG. 13, as an IF description modeling entry generated from the network element A, a class to which the class name “terminal pager off” is assigned, a class to which the class name “show ipv6 mld” is assigned, and “exit” The classes with the class name “are sequentially connected between“ process start ”and“ process end ”.

  In addition, as an IF description modeling entry generated from the network element B, a class with a class name “set terminal”, a class with a class name “show pim join extensible”, and a “show pim neighbors” A class to which a class name “inet6” is assigned and a class to which a class name “exit” is assigned are sequentially connected between “process start” and “process end”.

Then, “process start” and “process end” of the IF description modeling generated from the network element A are matched with “process start” and “process end” of the IF description modeling generated from the network element B, respectively.
Then, the class names of the objects connected between “process start” and “process end” are matched, and objects having class names that are inclusive or identical to each other are integrated into the same object. . The class name of the integrated object includes all the words constituting the class name of the object before integration.

  As a result, as shown in FIG. 14, the object with the class name “terminal pager off” in FIG. 13 and the object with the class name “set terminal” are integrated, and the object before integration is integrated. A class name “set, terminal, pager off” including all words constituting the class name is given. Further, the object “exit” to which the same class name is assigned is integrated, and the class name “exit” is given.

Next, after integrating objects with class names that are inclusive or identical to each other into the same object, the remaining objects that have not yet been integrated are Integrate.
As a result, as shown in FIG. 15, the object given the class name “show ipv6 mld” in FIG. 14, the object given the class name “show pim join extensible”, and the “show pim neighbors inet6” And the class name “show ipv6 mld, show pim join extensible, show pim neighbors inet6” including all the words constituting the class name of the object before the integration.

Note that the IF description modeling attributes (actual dialog description, NE vendor information) held in the IF description database 105 before integration are all held as independent IF description modeling attributes after integration.
When the processing so far is completed, the IF description modeling unit 104 notifies the test IF description blending unit 109 of the ID. The ID notified to the test IF description composition unit 109 at this time is the ID of the database table after integration. Here, the ID of the test IF description with the old existing number is used as the ID of the database table after integration. When receiving the ID from the IF description modeling unit 104, the test IF description blending unit 109 searches the IF description database 105 for the dialog attribute of the command description unit and its summary attribute using the ID as key information. Then, when searching for the summary attribute of the instruction description unit from the IF description database 105, the test IF description composition unit 109 generates a plurality of command character strings by rearranging the keywords constituting the summary attribute. Then, the conversion dialogue description is generated by replacing the command character string of the dialogue attribute, and is stored in the command description portion table 105c. Here, since a plurality of IF descriptions are used, a plurality of combination commands can be generated. For example, in the example of FIG. 15, the words included in the class name “show ipv6 mroute” such as “show ipv6 mld, show pim join extensible, show pim neighbors inet6” can be arbitrarily rearranged, and “show6” Commands such as “show neighbors inet6”, “show neighbors ipv6” can be generated. Thereby, the test IF information combining a plurality of scripts 21 can be generated, and a combination command capable of extracting an expected response as compared with the case where the test IF information is generated from one script 21. This makes it possible to automatically generate a script that conforms to the interface specifications of a newly introduced connection destination communication device.

Further, the IF description modeling unit 104 searches the NE command file 107 by a keyword. If the conversion rule for the keyword is defined in the NE command file 107, the conversion dialog description is generated by converting the keyword in the dialog description, and is stored in the command description part table 105c.
Further, the IF description modeling unit 104 searches the vocabulary conversion rule database 108 using keywords. When a synonym phrase or an antonym phrase of the vocabulary of the command character string is defined in the vocabulary conversion rule database 108, a conversion dialog description is generated by converting the command character string in the dialog description, and an instruction description section table Save to 105c.

  In this manner, a plurality of dialog descriptions in which the command character string is changed according to the keyword rearrangement of the command character string and the NE command file 107 or the vocabulary conversion rule database 108 are generated. These dialog attributes are stored in the IF description database 105 as attribute information in the same table as the original as a dialog description revised for the original dialog description.

  The present invention makes it possible to automatically generate a script that conforms to the interface specification of a newly introduced connection destination communication device, and can be used for an actual machine confirmation test of the interface specification for the network element of the network management device.

It is a block diagram which shows the example of schematic structure of the interface test apparatus by the interactive application which concerns on one Embodiment of this invention. It is a sequence diagram which shows the procedure from the script input in the interface test apparatus of FIG. 1 to storage of IF information for a test. It is a figure which shows one description example and decomposition | disassembly unit of the script of the interactive application which concerns on one Embodiment of this invention. It is a figure which shows the example of 1 description of the decomposition | disassembly rule of the interactive application which concerns on one Embodiment of this invention. It is a figure which shows one example of a description of the connection description part and command description part after substitution character substitution of the interactive application which concerns on one Embodiment of this invention. It is a figure which shows an example of the setting description part table 105a, the connection description part table 105b, and the instruction description part table 105c which are stored in IF description database 105 of FIG. It is a figure which shows an example of the keyword extraction method by IF description modeling part 104 of FIG. It is a figure which shows an example of the modeling method of the process of the script by IF description modeling part 104 of FIG. It is a figure which shows the example of 1 description of the NE command file 110 of FIG. It is a figure which shows an example of the content of the vocabulary conversion rule database 108 of FIG. It is a sequence diagram which shows the procedure from the terminal 5 of FIG. 1 to the input to each database and knowledge definition. It is a sequence diagram which shows the procedure of the palpation test to the network for a test using the test IF description produced | generated by the interface test apparatus of FIG. It is a figure which shows an example of the matching method of the modeled several process which concerns on one Embodiment of this invention. It is a figure which shows an example of the matching method of the modeled several process which concerns on one Embodiment of this invention. It is a figure which shows an example of the matching method of the modeled several process which concerns on one Embodiment of this invention.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Interface test apparatus 2 Network management apparatus 3 Service provision network 3a, 4a Network element 4 Test network 5 Terminal 21 Script 22 NE interface 101 IF input part 102 IF description decomposition part 103 Decomposition knowledge definition 104 IF description modeling part 105 IF description Database 105a Setting description part table 105b Connection description part table 105c Instruction description part table 106 Vendor knowledge definition part 107 NE command file 108 Vocabulary conversion rule database 109 Test IF description preparation part 110 IF palpation part

Claims (10)

Describes the contents of processing to be executed according to the contents of the command and the response, which is used for an interactive application in which one apparatus repeats the process of sending and receiving a command with a connection destination communication apparatus. A script collection means for collecting the collected scripts;
From the script collected by said script collection means, a summary attribute extraction means for extracting a predefined keyword, as an overview attributes representing features of the command content or the response content,
A script for the interface specification of a new connection destination communication device to be newly introduced by rearranging the summary attribute of the script that is extracted by the summary attribute extraction means and conforms to the interface specification of the already installed connection destination communication device Candidates are reconfigured, and among the script candidates, a script candidate that actually conforms to the interface specification of the newly introduced connection destination communication device conforms to the interface specification of the newly introduced connection destination communication device. A script generation device comprising script reconstruction means employed as a script. The summary attribute extraction means includes
Based on the decomposition knowledge definition, the script is decomposed into a setting description part, a connection description part, and a command description part, and is defined by a predefined character string condition in the connection description part and the command description part , and Script decomposition means for dividing the connection description part and the instruction description part into the dialog units, with a part set as a unit of processing in the connection description part and the instruction description part as one dialog ,
The keywords included either at least one of the connection description part and the instruction description unit and a keyword extracting unit configured to extract the conversation unit,
The script reconfiguring means includes:
By rearranging the keyword extracted by the keyword extracting unit by the interactive unit, according to claim, characterized in that it comprises a conversion dialog description generating means for generating a different conversion dialog description from the description of the interaction of pre recombinant 1 The script generator described. At least one of an NE command file that defines the conversion rule of the keyword, and a lexical conversion rule database that stores synonyms and antonyms of the vocabulary of the command character string configured by the keyword,
The script reconstruction means, said NE command file based on any one of at least one of the reference results of the lexical conversion rule database, the conversion interaction script generation apparatus according to claim 2, wherein the generating a description. Process modeling means for abstracting and expressing the process representing the flow of the script;
4. The script generation apparatus according to claim 2, further comprising process integration means for integrating a plurality of processes by comparing vocabularies and connection relationships between a plurality of processes for the same instruction. The process modeling means includes
And class generating means for generating a dialog description extracted in the interaction unit as a class,
And a class name assigning means for assigning to the class keywords extracted from the dialog description as the class name,
The process integration means includes
By integrating multiple processes, including a class integrating means to integrate the classes to each other included in each process,
5. The script generation apparatus according to claim 4, wherein the conversion dialog description generation unit generates the conversion dialog description by rearranging the keywords of the class integrated by the class integration unit in units of classes. Describes the contents of processing to be executed according to the contents of the command and the response, which is used for an interactive application in which one apparatus repeats the process of sending and receiving a command with a connection destination communication apparatus. Collecting the collected scripts,
In the collected script description , a part defined by a predefined character string condition and set as a unit of processing in the script is defined as one dialog, and the script description is decomposed into the dialog units. Steps,
Extracting predefined keywords included in the script, in the dialogue unit as an overview attributes representing features of the interaction,
By rearranging the summary attribute of the script that conforms to the interface specification of the connection destination communication device that has already been installed, the script candidate for the interface specification of the connection destination communication device that is newly introduced is reconfigured, and the script candidate A script candidate that actually conforms to the interface specification of the newly installed connection destination communication device is employed as a script that conforms to the interface specification of the newly installed connection destination communication device. Characteristic script generation method. Decomposing the script description into the dialog units comprises :
Based on the decomposition knowledge definition, setting description section the script, after decomposing the connection description part and instruction description unit, together with decomposed into each defining the setting description section, the connection description part and the instruction description unit wherein A step of disassembling into dialogue units,
The step of extracting the summary attribute for each interaction unit includes:
Extracting a command string from the instruction description unit has been in connection description section also decomposed into the interaction unit,
Extracting a keyword obtained by decomposing the command character string into units of words by referring to a delimiter,
Reconfiguring the script comprises:
The script generation method according to claim 6, further comprising: generating different dialog descriptions by changing the order of the keywords in the dialog units. Generating a class representing abstractly the dialog description decomposed into dialog units;
Assigning a keyword included in the class as a class name of the class;
Abstracting and expressing the connection relationship of the process representing the flow of the script by determining the connection relationship including the execution order or branching between the dialog descriptions;
Integrating multiple processes into one process by comparing vocabulary and connection relationships between multiple processes for the same instruction;
Assigning class names of a plurality of classes before integration as class names of classes constituting the integrated process;
The script generation method according to claim 7, further comprising: generating a different dialog description by replacing the order of the keywords in the unit of the integrated class. Describes the contents of processing to be executed according to the contents of the command and the response, which is used for an interactive application in which one apparatus repeats the process of sending and receiving a command with a connection destination communication apparatus. Collecting the collected scripts,
In the collected script description , a part defined by a predefined character string condition and set as a unit of processing in the script is defined as one dialog, and the script description is decomposed into the dialog units. Steps,
Extracting predefined keywords included in the script, in the dialogue unit as an overview attributes representing features of the interaction,
By rearranging the summary attribute of the script that conforms to the interface specification of the connection destination communication device that has already been installed, the script candidate for the interface specification of the connection destination communication device that is newly introduced is reconfigured, and the script candidate Of which, the computer adopts a step of adopting a script candidate that actually conforms to the interface specification of the newly installed connection destination communication device as a script that conforms to the interface specification of the newly installed connection destination communication device. A script generation program characterized by causing Describes the contents of processing to be executed according to the contents of the command and the response, which is used for an interactive application in which one apparatus repeats the process of sending and receiving a command with a connection destination communication apparatus. Collecting the collected scripts,
In the collected script description , a part defined by a predefined character string condition and set as a unit of processing in the script is defined as one dialog, and the script description is decomposed into the dialog units. Steps,
Extracting from script decomposed into the interaction unit, a predefined keyword, as an overview attributes representing features of the interaction,
Generating a class representing abstractly the dialog description decomposed into dialog units;
Constructing a process model expressing a connection relationship of processes representing the flow of the script;
While preserving the order relation dialog description of each script, and a step of integrating the process model of a plurality of script for each instruction type,
Based on the summary attribute of the pre-integration classes, extracting Class Summary attributes of the integrated process model,
By rearranging the summary attribute of the script that conforms to the interface specification of the connection destination communication device that has already been installed, the script candidate for the interface specification of the connection destination communication device that is newly introduced is reconfigured, and the script candidate Of which, the computer adopts a step of adopting a script candidate that actually conforms to the interface specification of the newly installed connection destination communication device as a script that conforms to the interface specification of the newly installed connection destination communication device. Script generation program characterized by letting

Images