JP3075664B2 - Communication protocol compatibility test equipment - Google Patents

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION The present invention relates to the Nth OSI reference model.
A communication protocol conformance test apparatus for testing whether a (N) -protocol specification is correctly implemented in a system in which a layer (hereinafter, referred to as "(N)-") protocol is implemented. About.

[0002]

2. Description of the Related Art Conventionally, in standardization of ITU and ISO, a test scenario for an OSI protocol conformance test is TTCN (Tree and Tabular Combined Notation).
Is described by a method combining a tree and a table.

The TTCN method describes all the items necessary for the test, such as the following. Test method Point of Control and Obser
vation), protocol data unit (PDU), and abstract service primitive (ASP)
(e.g., itive), etc. Test sequence describing the order in which events occur in the test scenario PDU and ASP parameter values for each event in the test sequence

[0004] Next, referring to FIG. 3, an MHS (Message Handling System) P1 / P which is one of the protocols of the application layer.
2 when testing the two protocols in the manner shown in FIG.
A test sequence by the CN will be described. In FIG. 3, the test sequence includes the name of the observed PCO (L), selection of input (!) / Response (?), And ASP name (R).
T-OPEN req), PDU name carried by ASP (MT
ABindArgument, etc.), assignment and comparison of variables (X: = 0)
) Are described line by line as observation events. In addition, as additional information of each event, a label (again
Etc.) and judgment (pass etc.) are described. The events occur in the order of the test sequence numbers (1, 2,...), But can be jumped to a specified line (third) by providing a label "again" as shown in the ninth in FIG. Also, as in the fourth, ninth, tenth, and eleventh response events in FIG. 3, response events at the same level represent selectable response events that can occur at that time. In addition, "? OTHER"
“WISE” represents all but the above events as selectable response events. "TIMEOUT" indicates that a time-out has occurred without receiving a predetermined response event. Further, in the observation event, a variable can be used so that a complicated conditional branch or result judgment can be described. For example, FIG. When the first event is executed, the value 0 is substituted for the variable X, and the event is regarded as being received under the condition that the value of the variable X is 3 in the fourth event. In the TTCN, a test scenario needs to be described until all branches are judged, and the judgment includes a pass (pass) and a fail (fail). And the test result is a pass or fail at each event of the test sequence.
Only the judgment of 1, fail2) is described. Note that the parameters of the ASP and PDU in each event are separately described by providing a table for each ASP and PDU.

In FIG. 2, reference numeral 100 denotes MHS P1 / P
Compatibility test device for 2 protocols, 200 is MHS P1
/ P2 protocol implemented system under test, 101 and 20
1 is a Reliable Transfer Service Entity (RTSE), which is a lower layer for the MHS P1 / P2 protocol.
ity).

[0006] In addition to the above-described method of creating a test scenario using the TTCN description as it is, referring to the description of the TTCN, the scenario of the N-th layer is represented by (N) -AS
State transition in a unique format in which actions to be executed are described in each column, with input events occurring for P, (N-1) -ASP and (N) -PDU as abscissa and state identification numbers as ordinate. There is also a method of creating a table.

[0007]

However, the above-mentioned TT
In the prior art in which a test scenario is created using the description by the CN as it is or as a reference, PCO, ASP
Since all necessary information such as PDUs and the like are described together in a test sequence, and further, it is necessary to describe the next input for every response, the description of the test scenario is complicated, and the amount of description is There is a problem that it takes a long time to create a test scenario.

Accordingly, an object of the present invention is to provide a communication protocol conformance test apparatus having a test scenario creation function capable of creating a test scenario in a short time.

[0009]

According to the first aspect of the present invention, there is provided an apparatus for testing the conformity of an (N) -protocol of a system which implements an Nth layer of an OSI reference model. Description of the test sequence, which is the order of the test events, setting of the parameters of the PDU independent of the description of the test sequence,
A test scenario creating means for creating a test scenario by setting the parameters of P independently of the description of the test sequence, a test executing means for performing a test facing the system under test based on the created test scenario, And a test result analysis means for analyzing test results. Further, in the invention of claim 2, the test scenario creation means uses (N) -PDU name when there is (N) -PDU to be transmitted and received, and (N) when there is no (N) -PDU. -1)-A test sequence editor that describes only a test sequence separately for those that transmit test events and those that receive test events by an ASP name, and (N) -PDU specifying test events in the test sequence.
PDU editor to set the parameters of (1) and (N-1) -AS by specifying the test event in the test sequence
And an ASP editor for setting parameters of P. According to a third aspect of the present invention, in the communication protocol conformance test apparatus, the test sequence editor has a function of selecting (N) -PDU name or (N-1) -ASP name from a preset menu. is there. The test sequence editor according to claim 4, wherein the test sequence editor is configured to execute the PD
A communication protocol conformance test device having a function of activating a U editor and the ASP editor. Further, in the invention according to claim 5, the PDU editor and the ASP editor are each stored in a created test scenario or as a test result.
A communication protocol conformance test apparatus characterized by having a function of using a PDU name, (N-1) -ASP name and their parameter values in PDU units and ASP units. Still further, the invention of claim 6 is the communication protocol conformance test apparatus, wherein the scenario creating means has a function of using the created test scenario for creating another test scenario.

[0010]

According to the first aspect of the present invention, a test scenario is created by independently describing a test sequence, setting a parameter of a PDU, and setting a parameter of a lower ASP, and performing a test based on the created test scenario. And analyze the test results. As described above, by independently setting the test sequence, setting the parameters of the PDU, and setting the parameters of the ASP, the description of the test sequence is simplified, and the setting of each parameter of the PDU and the ASP can be freely performed. Test scenarios can be created in a short time. According to the second aspect of the present invention, a test sequence editor, a PDU editor, and an ASP editor are used to create a test scenario.
Use two tools. In the test sequence editor, the test event is (N) -PDU name if there is (N) -PDU to be transmitted and received, and (N-1) -ASP name if there is no (N) -PDU. In the PDU editor, the test event in the test sequence is specified and the (N) -PDU parameter is set. In the ASP editor, the test in the test sequence is described. The event is specified and the (N-1) -ASP parameter is set. In this case, the description of the test sequence is further simplified by describing the test sequence only with the (N) -PDU name and the (N-1) -ASP name of the test event. In addition, by describing the test event (input) to be transmitted and the test event (response) to be received separately, the structure of the test sequence becomes clear and the description can be easily performed. In the invention of claim 3,
The test sequence can be described by selecting (N) -PDU name and (N-1) -ASP name from the menu. This further simplifies the description of the test sequence. According to the invention of claim 4, the test sequence editor activates the PDU editor and the ASP editor,
(N) -PDU and (N-1) -ASP parameters can be set, and these parameters can be easily set. According to the fifth aspect of the present invention, the (N) -PDU name, the (N-1) -ASP name and their parameter values in the created test scenario or stored as a test result are used in PDU units and ASP units. And (N) -PDU parameter setting and (N-1)
-ASP parameters can be set, and test scenario creation is further facilitated. In the invention of claim 6,
Another test scenario can be created by using the created test scenario, and thus the test scenario can be created in a short time.

[0011]

DESCRIPTION OF THE PREFERRED EMBODIMENTS The present invention will be described below with reference to the drawings (FIGS. 1, 2, and 4 to 33).

<Embodiment of Communication Protocol Compatibility Test Apparatus> The communication protocol suitability test apparatus shown in FIG. 1 includes a test scenario creation unit 10, a test execution unit 20, and a test result analysis unit 30. The compatibility test for each layer of the OSI reference model, for example, each protocol of the network layer or higher, can be arbitrarily selected and executed.

The test scenario creation unit 10 includes a test sequence, which is an order of input and response test events, for testing the conformity of the (N) -protocol of a system implementing an arbitrary Nth layer of the OSI reference model. Description and
A test for an arbitrary protocol is performed by setting (N) -PDU parameters independent of the description of the test sequence and by setting (N-1) -ASP parameters independent of the description of the test sequence. A scenario is selectively created. Specifically, a test sequence editor 11 and a PDU editor 12
And an ASP editor 13. The test sequence editor 11 uses the (N) -PDU name when the (N) -PDU to be transmitted / received exists, and the (N-1) -ASP name when the (N) -PDU does not exist. A function of selecting (N) -PDU name or (N-1) -ASP name from a preset menu, and a PDU editor. It has a function of activating the ASP editor 12 and the ASP editor 13. PDU editor 12
Is an editor for specifying the test event in the test sequence and setting the parameters of the (N) -PDU. The ASP editor 13 specifies the test event in the test sequence and sets the parameters of the lower (N-1) -ASP. Is an editor for setting parameter values of (N) -PDU and (N-1) -ASP in a created test scenario or stored as a test result in units of PDU and ASP. Have.

The test execution unit 20 performs a test in opposition to the system under test based on the created test scenario, and provides a test result to the test result analysis unit 30.

The test result analysis unit 30 analyzes the test result in comparison with the test scenario, and also stores the test result in a file. Specifically, the test result analysis unit 30 performs a test result sequence test. Analyzer 31
, A PDU analyzer 32 and an ASP analyzer 33. The test result sequence analyzer 31 mainly analyzes a sequence of events among the test results.
The received test event is classified, and the (N) -PDU name and (N-1) -ASP name are displayed or recorded with transmission / reception time and the like respectively. Further, the test result sequence analyzer 31 has a function of activating the PDU analyzer 32 and the ASP analyzer 33 by designating a test event. The PDU analyzer 31 analyzes the parameter values of the PDU of the test event received at the time of executing the test, and has a function of saving the analyzed parameter values of the PDU in a file. The ASP analyzer 32 analyzes the parameter values of the ASP of the test event received at the time of executing the test, and has a function of saving the analyzed parameter values of the ASP in a file.

<Example of Test Configuration for MHS P1 / P2 Protocol> Next, based on FIGS. 1, 2 and 4 to 27, the present invention will be described with reference to the seventh layer of the OSI reference model, ie, one of the protocols of the application layer. A configuration example and an operation example of a communication protocol compatibility test apparatus will be described by taking as an example a case where the present invention is applied to a test of a certain MHS P1 / P2 protocol. RTSE is a lower layer. Since the PDU of the MHS P1 / P2 protocol is carried by the RTSE, as shown in FIG. 2, the test in each of the RTSEs 101 including the P1 / P2 protocol PDU as the user data, ie, RT-
This is performed by transmitting and receiving ASP. Therefore, in the communication protocol conformance test apparatus shown in FIG. 1, the test sequence editor 11 describes the test sequence of the P1 / P2 protocol, the PDU editor 12 sets the parameters of the PDU of the P1 / P2 protocol, and the ASP editor 13 Then, the parameters of the RTSE ASP (RT-ASP) are set. The test result sequence analyzer 31 analyzes the test result sequence of the P1 / P2 protocol, and the PDU analyzer 32 analyzes the P1 / P2 protocol.
/ Analyze the parameter value of the PDU of the P2 protocol, and
The SP analyzer 33 uses the RTSE ASP (RT-AS
The parameter value of P) will be analyzed.

<Creation of Test Scenario for MHS P1 / P2 Protocol> Based on FIG. 1 and FIGS.
An example of creating a test scenario for the SP1 / P2 protocol will be described. As shown in the test scenario creation flowchart of FIG. 4, at the start of the test scenario creation, the input unit 40 designates whether or not to create a new test scenario in the test scenario creation unit 10. When creation of a new test scenario is designated, the test sequence editor 11 is started. If not, the name of the created test scenario is input to call up the test scenario file and the test sequence editor 11 is started. When the test sequence editor 11 is started, the description of the test event for the test sequence, the selection of cut, copy, paste and the like for partial cut and paste of the test sequence, the selection of the PDU editor, the ASP editor are performed according to the flowchart shown in FIG. Select, save scenario, end, etc. When the PDU editor is selected, the PDU editor is activated and operates according to the flowchart shown in FIG. When the ASP editor is selected, the ASP editor is activated and operates according to the flowchart shown in FIG.

[Description of Test Sequence] Based on FIGS. 1, 5 and 8 to 14, a test sequence editor 1
1 will be described. The test apparatus has an input unit and an image display unit 50 as shown in FIG.
As shown in the description example, the test event transmitted by the test apparatus to the system under test (input test event) is entered in the input field of the display screen, and the test event to be received by the test apparatus from the system under test (response test event) Are divided into response columns, respectively, and are entered in the input unit 40 to be described in the order of test events and recorded in a file.
Each test event is basically "MTABindArgum
Described by the PDU name of the MHS P1 / P2 protocol, such as “ent” or “Message.” However, “RT-TRANSF”
When an RT-ASP that does not have a PDU name of the same protocol such as “ERconf” is transmitted and received, the RT-A
Describe the SP name.

The description example of FIG. 8 shows that the test apparatus is “MTABindA”.
rgument "is transmitted to the system under test to request connection establishment. On the contrary, as shown in FIG. 9, the system under test transmits" MTABindArgument "to the test apparatus. By doing so, a test sequence that requires connection establishment can be described.

A test event can be described by selecting from a list menu as shown in FIG. Therefore, the test sequence editor 11 has a menu file, which is displayed on the screen of the display unit 50. The list menu includes a sequence control command for controlling a test sequence in addition to each PDU name of the MHS P1 / P2 protocol and each RT-ASP name.

The sequence control command includes "LOO
P ”,“ END OF LOOP ”, and“ WAIT. ”The“ LOOP ”command is obtained by adding“ EN ”
A test event in a range (in a loop) surrounded by these commands up to the D OF LOOP command is
This indicates that the command is repeatedly executed the number of times specified by the “LOOP” command. The “WAIT” command indicates to wait a specified number of seconds before processing the next test event. Therefore, the description example in FIG. 11 is a test sequence for transmitting “Message” three times every 10 seconds.

Further, an auxiliary symbol can be added to each test event so as to operate in association with a subsequent test event. Therefore, the test sequence editor 11 has an auxiliary symbol menu file as shown in FIG.
Then, by specifying a test event and selecting an auxiliary symbol to be added from the auxiliary symbol menu, an auxiliary symbol can be added. Supplementary symbols are used as follows. Auxiliary symbol "/": When the order in which a plurality of response test events are received is undefined, the auxiliary symbol "/" is used as shown in FIG. The supplementary symbol “/” added to the fourth and fifth lines in the description example of the test sequence in FIG.
Lines 6 to 6 indicate that “MTABindResult” having a different connection number, which is an ASP parameter value, may be received from any connection number. Auxiliary symbol ">": When a parameter value of an input test event is specified at the time of test execution, an auxiliary symbol ">" is used as shown in FIG. In the description example of FIG. 11 described above, the test event in the loop is executed with the same parameter value. However, when it is desired to change the parameter value of “Message” for each loop, “>” is used as shown in FIG. To describe the test sequence. Therefore, the supplementary symbol “>” in the fifth line in FIG. 14 indicates that the test execution can be interrupted in the fifth line during the test execution, the PDU parameter or the ASP parameter can be designated, and then the test execution can be resumed. Is shown. Auxiliary symbol "+": The auxiliary symbol "+" is used when it is desired to connect PDUs, and the details will be described later with reference to FIG. Auxiliary symbol "*": When the same response test event is received an unspecified number of times, the auxiliary symbol "*" is used, and details thereof will be described later with reference to FIG. Auxiliary symbol "?": The auxiliary symbol "?" Is used to indicate a response test event that does not need to be received. The details of this will be described later with reference to FIG.

In the flow chart of FIG. 5, when cut, copy, and paste are selected, for example, a test event of a plurality of lines in the already described test sequence is deleted,
Partial cutting and pasting such as copying can be performed, and the description work is facilitated.

[Input of PDU Parameter] The setting of the PDU parameter value by the PDU editor 12 will be described with reference to FIGS. 1, 5, 6, 8, and 15 to 19. To input PDU parameter values for each test event, select a test event and, as shown in FIG.
The editor 12 is started. Then, by using the manual unit 40 and the display unit 50, according to the flow shown in FIG. 6, all the parameters of the PDU of the input test event are set, and it is determined whether or not the parameters of the PDU of the response test event are correctly received. Set only what should be done. In FIG. 6, when newly setting the parameter value of the PDU, the PDU parameter is edited by the input unit 40, and then, if necessary, save and end are designated. In the storage, the input parameter values are encoded, and a file for reuse is created and stored by inputting a file name. At the end, the input parameter values are encoded and stored. When using the parameter values of the PDU previously set from the beginning, or when using the parameter values of the PDU stored in the test result analysis unit 30, the PDU parameter file is called by inputting a file name or the like, A desired parameter setting is edited using the decoded PDU parameter.

FIG. 15 shows a test event “MTABindA” on the first line in the test sequence illustrated in FIG.
rgument "on the screen side in the PDU editor 12. Here, the PDU of the application layer of the OSI reference model is shown.
Is ASN. 1 (Abstract Syntax Notation 1), a set of unordered parameters (SET), and selection from multiple parameters (CHO)
It has a tree structure combining data structures such as ICE). Therefore, as the setting of individual parameter values in the PDU editor 12, for the leaf of the above-described tree structure,
A character string or a numerical value is input in a format such as "IA5 String" or "INTEGER". For example, in the SET screen example of FIG.
When "r-name (MTAName)" is selected, the screen shown in Fig. 16 is displayed, and the input of a character string is requested in the format of "IA5String." Therefore, the required character string is input as a parameter value. In the screen example of FIG. 15, "initiator-cred
If you select “entials (Initiator Credientials)”, the CHOICE screen shown in FIG. 17 is displayed.
(Password) ”and“ strong (Strong Crediential) ”. So, for example, "si
3ple (Password) ”
The E screen is displayed, where “IA5String” and “OCT”
ET STRING "is requested. For example, if" IA5String "is selected, a screen shown in FIG. 19 is displayed, and a character string input is requested for the first time. Enter as a parameter value.

[Input of ASP Parameters] An example of setting the parameter values of the ASP by the ASP editor 13 will be described with reference to FIGS. 1, 5, 5 and 20 to 22.
To input an ASP parameter value for each test event, the test event is selected, and the ASP editor 13 is started in the test sequence editor 11 as shown in FIG. Then, the manual power unit 40 and the display unit 50
Using the flow shown in FIG. 7, all the parameters of the ASP of the input test event are set, and only the parameters of the ASP of the response test event for which it is determined whether or not it has been correctly received are set. In FIG. 7, when newly setting the parameter value of the ASP, the editing of the ASP parameter is performed by the input unit 40, and then the saving and the ending are designated as required. In saving, the input parameter values are created and saved as a file for reuse by inputting a file name. At the end, the entered parameter values are saved. Also,
When using the previously set ASP parameter values from the beginning, or when the A stored in the test result analysis unit 30 is used.
When using the parameter value of the SP, the file of the ASP parameter is called by inputting a file name or the like, and the AS parameter is called.
A desired parameter setting is edited using the P parameter.

When the ASP editor 13 starts, the ASP
For example, FIG.
0 and the screen shown in FIG. 21 are displayed. The screen example of FIG. 20 shows the ASP editor 1 for the test event (MTABindArgument) on the first line in the test sequence of FIG.
The screen example of FIG. 21 shows the test event (MTABindResul) on the second line in the test sequence of FIG.
12 is a screen of the ASP editor 13 for t). In response to such a screen, the input unit 40 inputs and sets the ASP parameters. FIG. 22 shows a screen display example in a state where the parameter values have been input to the screen of FIG. By the way, as the parameter value, FIG.
“Acceptance”, as for “Result” in
For those that take only limited values such as “ACS rejected” and “PL user rejected”, a table of these parameter values is prepared in the ASP editor 13 in advance for simplification of input, and this table, ie, menu You can choose from. On the other hand, "CEP-I
In the case of parameter values that can take any value, such as those relating to “D”, “Responding presentation address”, etc., enter as many numerical values and character strings as necessary according to the data type. For simplicity of input, the value to be transmitted and the value to be received during the test execution can be directly specified, for example, in the “Responding presentation address”, the ASP on the first line in the test sequence of FIG. The parameter “Called prese of“ RT-OPENind ”
ntationaddress "" parameter value
As shown in FIG. 22, a line number 1 is added and “1.
sentation address ".

<Configuration Operation of Test Execution Unit> FIGS. 1 and 1
The test execution unit 20 will be described based on FIG. 1, FIG. 14 and FIG. Using the test scenario created by the test scenario creating unit 10, the test execution unit 20 interprets the test sequence one line at a time in the order of the number of the test event, performs a test facing the system under test, and tests the test result. The test results are stored in a file to be passed to the result analyzer 30. When the test event is an input test event, the test execution unit 20 transmits a PDU and an ASP to the system under test. This transmission is basically performed after waiting for a transmission standby time set in advance as a fixed value. However, as in the input test event on the fifth line of the test sequence in FIG. 11, the input test immediately after the "WAIT" command is performed. In the case of an event, transmission is performed after waiting for a time specified by the “WAIT” command, for example, 10 seconds.
On the other hand, if the test event is a response test event, the test execution unit 20 waits until the PDU and ASP are received from the system under test, and the PDU name and the ASP name specified in the response test event, and their parameter values, The actually received PDU name, ASP name, and their parameter values are compared. If the result of the comparison is different, the test execution is terminated. In the reception of the response test event, the timeout time is provided as a fixed value, and if no reception is performed by this time, it is considered that the predetermined test event has not been received.

As shown in FIG. 23, the test execution unit 20 adds the transmission / reception time to the test event transmitted / received during the test execution and displays the test event in the same format as the test sequence.
0 is displayed on the screen. The test execution unit 30 stores the transmitted and received test events, the parameter values of the PDU and ASP, and the transmission and reception time in a file.

Further, the test execution section 20 can interrupt the test execution by selecting a temporary stop of the test during the test execution by the input section 40 or the like, and can interrupt the test execution by selecting a restart of the test. The test execution can be resumed from the test event. In the case of an input test event to which an auxiliary symbol “>” is added, such as the input test event on the fifth line of the test sequence in FIG. 14, the test execution unit 20 transmits the input test event before transmitting the input test event. Then, the test execution is interrupted so that the parameters can be set, and the test sequence editor 11 and the test result analyzer 31 for the test scenario being executed are started. With the interruption of the test execution, the parameters of the input test event to which the auxiliary signal “>” is added can be changed by the tools 11 and 31 by using the PDU parameter value or the ASP parameter value in the test result newly or partially executed. So that you can type. When the parameter input is completed, the test execution is resumed from the interrupted test event by activating the test execution restart on the test execution screen or the like.

<Configuration Operation of Test Result Analysis Unit> The test result analysis unit 30 will be described with reference to FIGS. 1, 11, and 24 to 27. The test result sequence analyzer 31 of the test result analysis unit 30 mainly analyzes a sequence of events among the test results. The test result sequence analyzer 31 separates a test event actually transmitted during a test execution from a test event actually received, (N) -PDU name and (N-1) -ASP name are displayed or recorded with transmission / reception time and the like respectively. FIG. 23 shows an example of the screen display, which shows the result of executing the test scenario of FIG.
This is displayed on the screen by the test result sequence analyzer 31. When analyzing the parameter values of the PDU and the ASP, the test result sequence analyzer 31
Then, the PDU analyzer 32 and the ASP analyzer 33 are started by designating a test event. The PDU analyzer 32 stores the PD of the test event transmitted and received during the test execution.
The parameter value of U is analyzed, the parameter value of the analyzed PDU is displayed, and saved in a file. FIG. 25 and FIG.
Each screen example of FIG. 6 shows a screen display of an analysis result by the PDU analyzer 32 with respect to the test event on the first line in FIG. The ASP analyzer 33 analyzes the parameter values of the ASP of the test event transmitted and received at the time of test execution, displays the analyzed parameter values of the ASP, and saves the file in a file. The screen example of FIG.
The screen display of the analysis result by the ASP analyzer 33 with respect to the test event on the line is shown.

<Example of Test Configuration for Session Layer (SL) Protocol> Next, FIGS. 1, 4 to 7 and FIGS. 28 to 3
3, a configuration example and an operation example of a communication protocol conformance test apparatus will be described by taking, as an example, a case where the present invention is applied to a test of a protocol of a fifth layer, that is, a session layer (SL) of an OSI reference model. Since the PDU (SPDU) of the session layer (SL) protocol is carried by the transport layer (TL), the test includes the SPDU of the SL protocol as user data as shown in FIG.
03, that is, T-ASP is transmitted and received. Therefore, in the communication protocol conformance test apparatus shown in FIG. 1, the test sequence editor 11 describes the test sequence of the SL protocol, and the PDU editor 12 sets the parameters of the SPDU of the SL protocol.
The SP editor 13 sets the parameters of the T-ASP of the TL. The test result sequence analyzer 31 analyzes the test result sequence of the SL protocol, and the PDU analyzer 32 analyzes the parameter value of the SPDU of the SL protocol.
In 3, the parameter value of the T-ASP of the TL is analyzed. Therefore, only the target protocol, the PDU name, the ASP name and their parameters are different.
Same as for the HS P1 / P2 protocol.

<Creation of Test Scenario for SL Protocol> An example of preparation of a test scenario for SL protocol will be described with reference to FIGS. 1, 4 to 7 and 29. As shown in the test scenario creation flowchart of FIG. 4, at the start of the test scenario creation, the input unit 40 designates whether or not to create a new test scenario in the test scenario creation unit 10. When creation of a new test scenario is designated, the test sequence editor 11 is started. If not, the name of the created test scenario is input to call up the test scenario file and the test sequence editor 11 is started. Test sequence editor 11
Is activated, according to the flowchart shown in FIG.
The description of the test event for the test sequence, the selection of cut, copy, paste, etc. for partial cut and paste of the test sequence, the selection of the PDU editor, the selection of the ASP editor, the saving of the scenario, the termination, etc. are specified. When the PDU editor is selected, the PDU editor is activated and operates according to the flowchart shown in FIG. When the ASP editor is selected, the ASP editor is activated and operates according to the flowchart shown in FIG.

[Description of Test Sequence] The description of the test sequence by the test sequence editor 11 will be described with reference to FIGS. 1, 5 and 29. The test apparatus has an input unit 40 and a display unit 50 as shown in FIG. 1. As shown in a description example in FIG. 29, a test event (input test event) transmitted from the test apparatus to the system under test is input on the display screen. In addition, test events (response events) to be received from the system under test by the test apparatus are respectively classified into response columns, and are entered in the input unit 40 and described in the order of the test events and recorded in a file. Each test event is basically an S like “CN” or “AC”.
Described by the SPDU name of the L protocol. However, "TC
When a T-ASP that does not have an SPDU name of the same protocol such as “ONNETreq” is transmitted / received, the T-ASP name is described.

The description example of FIG. 29 shows that the test apparatus is "T-CON
This is an example of a test sequence in a case where a connection establishment is requested by transmitting “NECTreq” to the system under test.
It is also possible to describe a test sequence that requests the establishment of a connection by transmitting "ONCONNECTind" to the test apparatus.

A test event can be described by selecting it from a list menu. Therefore, the test sequence editor 11 has a menu file, which is displayed on the screen of the display unit 50. The list menu includes, in addition to each SPDU name of the SL protocol and each T-ASP name, an appropriate sequence control command for controlling a test sequence. For example, a “WAIT” command indicates that the process waits for a specified number of seconds before processing the next test event. Therefore, the description example in FIG. 29 is a test sequence for transmitting “MIA” three times every 10 seconds.

An auxiliary symbol can be added to each test event so as to operate in association with a subsequent test event. Therefore, the test sequence editor 11 has an auxiliary symbol menu file as shown in FIG.
Then, a test event is specified, and an auxiliary symbol to be added is selected from the auxiliary symbol menu as described above, thereby adding an auxiliary symbol. An auxiliary symbol “+” added to each test event on the fifth, eighth, tenth, and fifteenth lines in the sequence description example of FIG. 29 is for connecting PDUs. Therefore, in the fifth line of FIG. 29, two SPDUs “AS” and “GT” in the next line are connected, and one T-ASP called “T-DATAreq”.
Meaning to carry by. An auxiliary symbol “*” added to the test event on the seventh line in the test sequence description example of FIG. 29 indicates that the same response test event is received an unspecified number of times. Therefore, in the example of the seventh line in FIG.
This means that the SPUD “DT” is repeatedly received. Further, the auxiliary signal “?” Added to the test event on the 18th line in the test sequence description example of FIG. 29 indicates a response test event that need not be received. Therefore, in the example of FIG. 29, when “MIA” is not received by the timeout time specified by the “WAIT” command,
Although it is considered that "MIA" has not been received, it means that the test execution of the test event of the next line can be performed without interruption. However, in the case where the immediately following line is a response test event, like the auxiliary symbol “?” On the seventh line in the description example of the test sequence in FIG. When the "MIP" on the line is received,
The “DT” on the seventh line is regarded as not received, and means that the test execution of the next test event on the ninth line is started. Here, the description example of FIG. 30 is a test sequence in a case where the system under test requests connection establishment by transmitting “T-CONNECTind” to the test apparatus.

In the case of the SL protocol as well, when cut, copy, and paste are selected in the flowchart of FIG. 5, partial cut and paste, such as deleting or copying a plurality of lines of test events in the already described test sequence, is performed. Can be performed, and the description work is facilitated.

[Input of SPDU Parameters] Setting of SPDU parameter values by the PDU editor 12 will be described with reference to FIGS. 1, 5, 6, 31, and 32.
To input SPDU parameter values for each test event of the SL protocol, select a test event and, as shown in FIG.
In step 1, the PDU editor 12 is started. Then, using the manual unit 40 and the display unit 50, all the parameters of the SPDU of the input test event are set according to the flow shown in FIG. 6, and it is determined whether or not the parameters of the SPDU of the response test event are correctly received. Set only what should be done. In FIG. 6, when newly setting the parameter value of the SPDU, the PDU parameter is edited by the input unit 40, and then, if necessary, save and end are designated. In the storage, the input parameter values are encoded, and a file for reuse is created and stored by inputting a file name. At the end, the input parameter values are encoded and stored. Also,
When using the parameter value of the SPDU previously set from the beginning, or when using the parameter value of the SPDU stored in the test result analysis unit 30, the file of the PDU parameter is called by inputting a file name or the like,
A desired parameter setting is edited using the decoded PDU parameter.

FIG. 31 shows the P for the test event "CN" on the third line in the test sequence illustrated in FIG.
A screen display example in the DU editor 12 is shown. FIG. 32 shows the test event “D” on the 13th line in FIG.
An example of a screen display of the PDU editor 12 corresponding to "T" is shown. When a communication protocol conformance test of a lower layer in the OSI reference model such as the session layer SL is performed, a protocol of an upper layer is performed. Must be carried as the user data of the SPDU. Therefore, the upper layer PDU carried as the user data is separately created by the PDU editor for the upper layer (presentation layer PL for SL) and saved as a user data file. Then, in the SL, the user data file is divided and transmitted by the PDU editor 12. To provide such a function of dividing and transmitting the user data file, as shown in FIG. In the PDU editor 12 for the PDU including the user data, the user data file is designated. User data fail), the starting address to be cut out (User data offset), and the number of bytes to be cut out (User data bytes) can be set, and an upper layer PDU editor for creating and saving a user data file. Also test sequence editor 11
You can choose to start from.

[Input of ASP Parameter] An example of setting the T-ASP parameter value by the ASP editor 13 will be described with reference to FIGS. 1, 5, 5, and 33. To input a T-ASP parameter value for each test event, the test event is selected, and the ASP editor 13 is started in the test sequence editor 11 as shown in FIG. Then, the manual power unit 40 and the display unit 50
By using the flow shown in FIG. 7, all the parameters of the T-ASP of the input test event are set, and the parameters of the T-ASP of the response test event are set only for those for which it is determined whether or not they have been correctly received. I do. FIG.
In the case of setting a new ASP parameter value, the ASP parameter is edited by the input unit 40, and then, if necessary, save and end are designated. In saving, the input parameter values are created and saved as a file for reuse by inputting a file name. At the end, the entered parameter values are saved.
Also, when using the T-ASP parameter values set previously from the beginning, or when using the T-ASP parameter values stored in the test result analysis unit 30,
The file of the ASP parameter is called by inputting a file name or the like, and a desired parameter setting is edited using the ASP parameter.

When the ASP editor 13 starts, the ASP
For example, FIG.
The screen shown in FIG. 3 is displayed. The screen example of FIG. 33 shows the ASP editor 1 for the test event (T-CONNECTreq) on the first line in the test sequence of FIG.
3 is a screen. In response to such a screen, the input unit 4
By setting 0, an ASP parameter is input and set. For parameters that take only limited values as parameter values, a table of these parameter values is prepared in advance in the ASP editor 13 for simplification of input, and can be selected from this table, that is, a menu. On the other hand, in the case of a parameter value that can take an arbitrary value, a necessary number of numerical values and character strings are input as they are according to the data type. Further, as parameter values, values to be transmitted and received during test execution can be directly specified for simplification of input.

<Configuration Operation of Test Execution Unit> FIGS. 1 and 29
The test execution unit 20 will be described based on the following. The test execution unit 20 for the SL protocol uses the test scenario created by the test scenario creation unit 10 to interpret the test sequence one line at a time in the order of the number of the test event, and performs a test facing the system under test. The result is stored in a file to be passed to the test result analysis unit 30. If the test event is an input test event,
The test execution unit 20 transmits the SPDU and the T-ASP to the system under test. This transmission is basically performed after waiting for a transmission standby time set in advance as a fixed value. However, as in the input test event on line 17 of the test sequence in FIG. 29, the input test immediately after the “WAIT” command is performed. In the case of an event, transmission is performed after waiting for a time specified by the “WAIT” command, for example, 20 seconds. On the other hand, if the test event is a response test event, the test execution unit 20 waits until an SPDU and a T-ASP are received from the system under test, and the SPDU name, the T-ASP name designated by the response test event, and those names. Parameter value, SPDU name actually received, T-ASP
Names and their parameter values. As a result of the comparison,
If not, the test execution is terminated.
In the reception of the response test event, the timeout time is provided as a fixed value, and if no reception is performed by this time, it is considered that the predetermined test event has not been received.

The test execution unit 20 displays the test event of the SL protocol transmitted and received at the time of test execution in the same format as the test sequence by attaching the transmission and reception time.
Is displayed on the screen. Also, the test execution unit 2
0 stores the transmitted / received test event, the parameter values of the SPDU and T-ASP, and the transmission / reception time in a file.

Further, the test execution section 20 can interrupt the test execution by selecting the test suspension during the test execution by the input section 40 or the like, and can interrupt the test execution by selecting the test restart. The test execution can be resumed from the test event. Also, in the case of the SL protocol, in the case of the SL protocol, in the case of the input test event to which the supplementary symbol “>” is added, as in the case of the input test event, the parameter can be set before transmitting the input test event. Thus, the test execution is interrupted, and the test sequence editor 11 and the test result analyzer 31 for the test scenario being executed are started. Due to the interruption of the test execution, the parameters of the input test event to which the auxiliary signal “>” has been added can be input using the PDU parameter value or the ASP parameter value in the test result newly or partially executed. I have to. When the parameter input is completed, the test execution is resumed from the interrupted test event by activating the test execution restart on the test execution screen or the like.

<Configuration Operation of Test Result Analysis Unit> Next, the test result analysis unit 30 will be described. The test result sequence analyzer 31 of the test result analysis unit 30 of the SL protocol mainly analyzes a sequence of events among the test results. The test result sequence analyzer 31 compares a test event actually transmitted at the time of test execution and a test event actually received at the time of test execution. It classifies and displays or records the SPDU name and the T-ASP name with the transmission / reception time, etc., respectively. Also, SPDU
When analyzing the parameter values of T-ASP and T-ASP, the test result sequence analyzer 31 designates a test event and starts the PDU analyzer 32 and the ASP analyzer 33. The PDU analyzer 32 analyzes the parameter value of the SPDU of the test event transmitted and received at the time of the test execution, and displays the parameter value of the analyzed SPDU.
Also save it to a file. The ASP analyzer 33 analyzes the T-ASP parameter values of the test event transmitted and received during the test execution, displays the analyzed T-ASP parameter values, and saves the file in a file.

Although the above-described embodiment is directed to the conformity test of each protocol of the application layer and the session layer of the OSI reference model, the present invention is not limited to this, and the same applies to the conformity test of the other N-th layer protocols. The present invention can be applied to

[0048]

According to the first aspect of the present invention, a test scenario is created by independently describing a test sequence, setting PDU parameters, and setting ASP parameters, and testing based on the created test scenarios. And analyze the test results. As described above, by independently setting the test sequence, setting the parameters of the PDU, and setting the parameters of the ASP, the description of the test sequence is simplified, and the setting of each parameter of the PDU and the ASP can be freely performed. Test scenarios can be created in a short time. According to the second aspect of the present invention, a test sequence editor, a PDU editor, and an ASP editor are used to create a test scenario.
Use two tools. In the test sequence editor, the test event is (N) -PDU name if there is (N) -PDU to be transmitted and received, and (N-1) -ASP name if there is no (N) -PDU. In the PDU editor, the test event in the test sequence is specified and the (N) -PDU parameter is set. In the ASP editor, the test in the test sequence is described. The event is specified and the lower (N-1) -ASP parameters are set. In this case, the test sequence is defined as (N) -PDU name and (N-1) -ASP of the test event.
Describing the test sequence only by the name further simplifies the description of the test sequence. Further, by separately describing the test event (input) to be transmitted and the test event (response) to be received, the structure of the test sequence becomes clear, and the description can be easily performed. The test sequence can be described by selecting (N) -PDU name and (N-1) -ASP name from the menu. This further simplifies the description of the test sequence. According to the fourth aspect of the present invention, the PDU editor and the ASP editor can be activated by the test sequence editor to set the parameters of (N) -PDU and (N-1) -ASP, and can easily set these parameters. It can be carried out. According to the fifth aspect of the present invention, the (N) -PDU name, the (N-1) -ASP name and their parameter values in the created test scenario or stored as a test result are used in PDU units and ASP units. And (N) -PDU parameter setting and (N-
1)-ASP parameters can be set, and test scenario creation is further facilitated. According to the sixth aspect of the present invention, another test scenario can be created using the created test scenario, so that the test scenario can be created in a short time.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration example of a communication protocol conformance test device of the present invention.

FIG. 2 is a diagram showing a test outline of an MHS P1 / P2 protocol.

FIG. 3 is an explanatory diagram of a conventional test scenario creation by TTCN.

FIG. 4 is a diagram showing a schematic flow of creating a test scenario in the present invention.

FIG. 5 is a diagram showing an operation flow of a test sequence editor.

FIG. 6 is a diagram showing an operation flow of a PDU editor.

FIG. 7 is a diagram showing an operation flow of an ASP editor.

FIG. 8 is a diagram showing an example of a screen display of a test sequence for the MHS P1 / P2 protocol.

FIG. 9 is a diagram showing a screen display of another example of the test sequence.

FIG. 10 is a diagram showing a screen display of a list menu.

FIG. 11 is a diagram showing an example of a screen display of a test sequence using a sequence control command.

FIG. 12 is a diagram showing a screen display example of an auxiliary symbol menu.

FIG. 13 is a view showing a screen display example of a test sequence including a test event to which an auxiliary signal is added.

FIG. 14 is a diagram showing a screen display example of a test sequence including a test event to which an auxiliary symbol is added.

FIG. 15: PD for MHS P1 / P2 protocol
The figure which shows the example of a screen in a U editor.

FIG. 16: PD for MHS P1 / P2 protocol
The figure which shows the example of a screen in a U editor.

FIG. 17: PD for MHS P1 / P2 protocol
The figure which shows the example of a screen in a U editor.

FIG. 18: PD for MHS P1 / P2 protocol
The figure which shows the example of a screen in a U editor.

FIG. 19: PD for MHS P1 / P2 protocol
The figure which shows the example of a screen in a U editor.

FIG. 20: AS for MHS P1 / P2 protocol
The figure which shows the example of a screen display in a P editor.

FIG. 21: AS for MHS P1 / P2 protocol
The figure which shows the example of a screen display in a P editor.

FIG. 22: AS for MHS P1 / P2 protocol
The figure which shows the example of a screen display in a P editor.

FIG. 23 is a diagram showing an example of a screen display when a test for the MHS P1 / P2 protocol is executed.

FIG. 24 is a diagram showing an example of a screen display of a test result for the MHS P1 / P2 protocol.

FIG. 25 is a diagram showing a screen display example of an analysis result of a PDU parameter value of a test result for the MHS P1 / P2 protocol.

FIG. 26 is a diagram showing a screen display example of an analysis result of a PDU parameter value of a test result for the MHS P1 / P2 protocol.

FIG. 27 is a diagram showing a screen display example of an analysis result of an ASP parameter value of a test result for the MHS P1 / P2 protocol.

FIG. 28 is a view showing a test outline of an SL protocol.

FIG. 29 is a diagram showing an example of a screen display of a test sequence for the SL protocol.

FIG. 30 is a diagram showing a screen display of another example of the test sequence.

FIG. 31 is a view showing an example of a screen in a PDU editor for the SL protocol.

FIG. 32 is a diagram showing an example of a screen in a PDU editor for the SL protocol.

FIG. 33 is a view showing a screen display example in an ASP editor for the SL protocol.

[Explanation of symbols]

 10 Test Scenario Creation Unit 11 Test Sequence Editor 12 PDU Editor 13 ASP Editor 20 Test Execution Unit 30 Test Result Analysis Unit 31 Test Result Sequence Analyzer 32 PDU Analyzer 33 ASP Analyzer

──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Kenji Suzuki 2-3-2 Nishi-Shinjuku, Shinjuku-ku, Tokyo International Telegraph and Telephone Corporation (56) References JP-A-62-292045 (JP, A) JP-A-1-221962 (JP, A) JP-A-2-1681 (JP, A) JP-A-4-107703 (JP, A) JP-A-5-122300 (JP, A) Int.Cl. ⁷ , DB name) H04L 29/14 H04L 29/06

Claims (6)

(57) [Claims] An apparatus for testing (N) -protocol conformance of a system implementing the Nth layer of the OSI reference model, comprising: a description of a test sequence which is an order of input and response test events; and a parameter of a PDU. Test scenario creation means for creating a test scenario by setting independent of the description of the test sequence described above, and setting independent of the description of the test sequence of the parameters of the lower-level ASP, based on the created test scenario And a test result analyzing means for analyzing a test result. 2. The method according to claim 1, wherein said test scenario creating means includes: (N) -PDU when there is an (N) -PDU to be transmitted / received.
If the same (N) -PDU does not exist, (N-
1) -Specify a test sequence editor that describes only a test sequence separately for those that transmit test events and those that receive test events, and specify test events in the test sequence (N).
-Specify a PDU editor to set PDU parameters, and specify a test event in the test sequence (N-
The communication protocol conformance test apparatus according to claim 1, further comprising: 1) an ASP editor for setting an ASP parameter. 3. The test sequence editor may select (N) -PDU name or (N-1) from a preset menu.
3. The communication protocol conformance test apparatus according to claim 2, wherein the apparatus has a function of selecting an ASP name. 4. The test sequence editor according to claim 1, wherein
The communication protocol conformance test apparatus according to claim 2, further comprising a function of activating a DU editor and the ASP editor. 5. The PDU editor and the ASP editor respectively include (N) -PDU name, (N) in a created test scenario or stored as a test result.
-1)-the ASP names and their parameter values
3. The communication protocol conformance test apparatus according to claim 2, wherein the apparatus has a function of using a unit and an ASP unit. 6. The communication protocol conformance test apparatus according to claim 1, wherein said scenario creating means has a function of using the created test scenario for creating another test scenario.