JPH07245641A - Communication protocol adaptability test equipment - Google Patents

Abstract

PURPOSE:To generate a scenario in a short time by forming a scenario generating section in a prescribed configuration to independently implement description of a test sequence and parameter setting for a protocol data unit(PDU) and a subordinate abstract service primitive (PSP). CONSTITUTION:The equipment testing the adaptability of an (N)-protocol of a system mounting an N-th layer of an OSI reference model is made up of a test scenario generating section 10, a test execution section 20 executing a scenario, and a test analysis section 30 or the like. The generating section 10 is made up of a test sequence editer 11, a PDU editer 12 and an ASP editer 13, and the description of a test sequence, setting of parameters of the PDU, ASP are implemented independently. Thus, the description of the test sequence is simplified and the degree of freedom of setting of each parameter is high and the test scenario is generated in a short time.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION The present invention relates to the Nth OSI reference model.
Communication protocol compatibility test device for testing whether or not the specifications of the (N) -protocol are correctly implemented for a system that implements a layer (hereinafter referred to as "(N)-") protocol. Regarding

[0002]

2. Description of the Related Art Conventionally, in the standardization of ITU and ISO, a test scenario for 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 items necessary for the test, such as the following. Test method PCO: Point of Control and Obser
vation), protocol data unit (PDU), and abstract service primitive (ASP).
positive sequence) Test sequence that describes the sequence of events in the test scenario. Parameter value of PDU or ASP in each event in the test sequence.

Next, referring to FIG. 3, MHS (Message Handling System) P1 / P which is one of application layer protocols.
TT when testing two protocols by the method shown in FIG.
The test sequence by the CN will be described. In FIG. 3, in the test sequence, the observed PCO is named (L), input (!) / Response (?) Is selected, and ASP name (R).
T-OPEN req), PDU name carried by ASP (MT
ABindArgument etc.), variable substitution and comparison (X: = 0
, Etc.) is described line by line as an observation event. In addition, a label (again
Etc.) and judgment (pass etc.). Although the events occur in the order of the test sequence numbers (1, 2, ...), it is possible to jump to the designated line (third) by providing the label again like the ninth in FIG. Moreover, like the 4th, 9th, 10th, and 11th in FIG. 3, the response events of the same level represent selectable response events that can occur at that time. Also, "? OTHER
"WISE" represents all but the above events as selectable response events, and "? "TIMEOUT" indicates that a predetermined response event has not been received and the time-out has occurred. 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. The value 0 is assigned to the variable X when the first event therein is executed, and it is considered that the variable X has been received under the condition that the value of the variable X is 3 at the fourth event. In the TTCN, the test scenario needs to be described until all branches can be judged, and there are pass (pass) and fail (fail) in the judgment, and the failure is a number (1, 2) for each reason. , Etc., and the test result is pass or fail at each event in the test sequence.
Only the judgment of 1 and fail 2) is described. The parameters of ASP and PDU in each event will be described separately by providing a table for each ASP and PDU.

In FIG. 2, 100 is MHS P1 / P
2 protocol compatibility tester, 200 is MHS P1
/ P2 protocol implementation system under test, 101 and 20
1 are Reliable Transfer Service Entities (RTSE: Reliable Transfer Service Ent), which are lower layers for the MHS P1 / P2 protocols.
ity) is shown.

In addition to the method of creating a test scenario which uses the above-mentioned description in TTCN as it is, a scenario in the Nth layer is referred to as (N) -AS by referring to the description in TTCN.
P, (N-1) -ASP and (N) -PDU is a state transition in a unique format in which the horizontal axis is the input event and the vertical axis is the state identification number and the action to be executed is described in each column. There is also a method of creating by using a table.

[0007]

However, the above-mentioned TT
In the conventional technology that uses the description in CN as it is or creates a test scenario with reference, PCO, ASP
The description of the test scenario is complicated and the amount of description is complicated because it is necessary to describe all the necessary information such as PDU and PDU in a test sequence, and further, it is necessary to describe the input to be performed next for every response. However, there is a problem that it takes a long time to create a test scenario.

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

[0009]

To achieve the above object, the present invention according to claim 1 is an apparatus for testing conformity of (N) -protocol of a system implementing layer N of the OSI reference model, in which an input and a response are provided. Of the test sequence, which is the order of the test events of the above, and the setting independent of the description of the test sequence of the parameters of the PDU, and the lower AS
A test scenario creating means for creating a test scenario by setting the parameters of P independently of the description of the test sequence; and a test executing means for conducting a test in opposition to the system under test based on the created test scenario. And a test result analysis means for analyzing a test result. According to the invention of claim 2, the test scenario creating means uses the (N) -PDU name when the (N) -PDU to be transmitted / received exists, and (N) -PDU when the (N) -PDU does not exist. -1) -Specify the test event in the test sequence by dividing the test event into one that sends the test event and one that receives the test event, and specify the test event in the test sequence (N) -PDU.
Specify the test event in the test sequence and the (N-1) -AS
An ASP editor for setting P parameters, and a communication protocol compatibility test apparatus characterized by the above. According to a third aspect of the present invention, in the communication protocol compatibility 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. In the invention of claim 4, the test sequence editor is the PD.
A communication protocol compatibility test apparatus having a function of activating a U editor and the ASP editor. Further, in the invention of claim 5, the PDU editor and the ASP editor are respectively saved in a created test scenario or as a test result (N)-
A communication protocol compatibility test apparatus having a function of using a PDU name, (N-1) -ASP name and their parameter values in PDU units and ASP units. Furthermore, the invention of claim 6 is the communication protocol compatibility 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, the description of the test sequence, the setting of the parameters of the PDU, and the setting of the parameters of the lower ASP are performed independently to create a test scenario, and the test is performed based on the created test scenario. And analyze the test results. In this way, by setting the test sequence, the parameter of the PDU, and the parameter of the ASP independently, the description of the test sequence is simplified and the setting of each parameter of the PDU and the ASP can be freely performed. It can be done, and thus test scenarios can be created in a short time. In the invention of claim 2, a test sequence editor, a PDU editor, and an ASP editor are used to create a test scenario.
Use one tool. Then, in the test sequence editor, if there is an (N) -PDU to be transmitted and received, the (N) -PDU name is used, and if the (N) -PDU does not exist, the (N-1) -ASP name is used and the test event Only the test sequence is described separately for sending and receiving, and the PDU editor specifies the test event in the test sequence and sets the (N) -PDU parameter, and the ASP editor tests for the test sequence. Specify the event and set the (N-1) -ASP parameters. 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 dividing the description into 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 performed easily. According to the invention of claim 3,
The test sequence can be described by selecting the (N) -PDU name and the (N-1) -ASP name from the menu. This further simplifies the test sequence description. In the invention of claim 4, the test sequence editor activates the PDU editor and the ASP editor,
The parameters of (N) -PDU and (N-1) -ASP can be set, and these parameters can be easily set. In the invention of claim 5, the (N) -PDU name, (N-1) -ASP name and their parameter values stored in the created test scenario or as the test result are used in PDU units and ASP units. Then, the parameter setting of (N) -PDU and (N-1)
-ASP parameters can be set, and test scenario creation becomes easier. In the invention of claim 6,
The created test scenario can be used to create another 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 accompanying drawings (FIGS. 1, 2, and 4 to 33).

<Embodiment of Communication Protocol Compatibility Testing Apparatus> The communication protocol compatibility testing apparatus shown in FIG. 1 comprises a test scenario creating section 10, a test executing section 20, and a test result analyzing section 30. , OSI reference model layers such as the network layer and higher protocols can be arbitrarily selected and executed.

The test scenario generator 10 tests the sequence of input and response test events in order to test the compatibility of the (N) -protocol of a system implementing any layer N of the OSI reference model. Description of
A test for an arbitrary protocol by the setting independent of the description of the test sequence of the (N) -PDU parameter and the independent setting of the description of the lower (N-1) -ASP parameter of the test sequence. A scenario is selectively created. Specifically, a test sequence editor 11 and a PDU editor 12 are provided.
And the 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, and the test event Is to describe only the test sequence by dividing it into one for sending and one for receiving, and a function for selecting (N) -PDU name or (N-1) -ASP name from a preset menu, and a PDU editor. 12 and the ASP editor 13 are activated. PDU editor 12
Is an editor for designating the test event in the test sequence and setting the parameters of the (N) -PDU, and the ASP editor 13 designates the test event in the test sequence and the parameters of the lower (N-1) -ASP. Is an editor for setting the parameter value of (N) -PDU, (N-1) -ASP in the created test scenario or saved as a test result, in units of PDU and ASP. Have

The test execution unit 20 conducts a test in opposition to the system under test based on the created test scenario, and provides the 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 saves the test result in a file. Specifically, the test result analysis unit 30 tests the test result sequence. Analyzer 31
And an ADA analyzer 32 and an ASP analyzer 33. The test result sequence analyzer 31 mainly analyzes the sequence of events in the test result, and includes the test event transmitted during the test execution,
The received test events are classified, and the (N) -PDU name and the (N-1) -ASP name are each attached with the transmission / reception time and displayed or recorded. Further, the test result sequence analyzer 31 has a function of designating a test event and activating the PDU analyzer 32 and the ASP analyzer 33. The PDU analyzer 31 analyzes the parameter value of the PDU of the test event received during the test execution, and has a function of saving the analyzed parameter value of the PDU in a file. The ASP analyzer 32 analyzes the ASP parameter value of the test event received during the test execution, and has a function of saving the analyzed ASP parameter value 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, that is, one of the application layer protocols. A configuration example and an operation example of the communication protocol compatibility test apparatus will be described by taking as an example the case of application to a test of a certain MHS P1 / P2 protocol. RTSE is a lower layer. Since the MHS P1 / P2 protocol PDUs are carried by the RTSE, the test, as shown in FIG. 2, includes the P1 / P2 protocol PDUs as user data.
It is performed by transmitting and receiving ASP. Therefore, in the communication protocol compatibility 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 P1 / P2 protocol PDU, and the ASP editor 13 Then, the parameter of RTSE ASP (RT-ASP) is set. Also, the test result sequence analyzer 31 analyzes the test result sequence of the P1 / P2 protocol, and the PDU analyzer 32 analyzes P1.
/ P2 protocol PDU parameter value is analyzed,
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 FIGS. 1 and 4 to 27, MH
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 test scenario creation, the test scenario creation unit 10 is instructed by the input unit 40 whether or not a new test scenario is created. When a new test scenario creation is specified, the test sequence editor 11 is activated. If not, the created test scenario name is input to call the test scenario file and the test sequence editor 11 is activated. When the test sequence editor 11 is started, the test event description for the test sequence, the cut / copy / paste selection for partial cut / paste of the test sequence, the selection of the PDU editor, the ASP editor are performed according to the flowchart shown in FIG. Specify, 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, the test sequence editor 1
The description of the test sequence in 1 will be described. The test apparatus has an input unit and an image display unit 50 as shown in FIG.
As in the description example shown in, the test event sent by the test equipment to the system under test (input test event) is displayed in the input field of the display screen, and the test event that the test equipment should receive from the system under test (response test event). Are divided into response fields, which are described in the order of test events by inputting from the input unit 40 and recorded in a file.
Each test event is basically a “MTABindArgum
Described by PDU name of MHS P1 / P2 protocol such as "ent" or "Message", provided that "RT-TRANSF"
When an RT-ASP that does not have a PDU name such as ERconf ”is sent / received, the RT-A
Describe the SP name.

In the description example of FIG. 8, the test apparatus is "MTABindA.
This is an example of a test sequence when requesting establishment of a connection by transmitting "rgument" to the system under test. On the contrary, the system under test transmits "MTABindArgument" to the test equipment as shown in FIG. By doing so, it is possible to describe a test sequence that requires connection establishment.

A test event can be described by selecting it 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 each PDU name of the MHS P1 / P2 protocol, each RT-ASP name, and a sequence control command for controlling the test sequence.

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

In addition, an auxiliary symbol can be added to each test event in order to operate in association with the subsequent test event. Therefore, the test sequence editor 11 has a file of the supplementary symbol menu as shown in FIG. 12, which is displayed on the screen of the display unit 50.
Then, by designating a test event and selecting the auxiliary symbol to be added from the auxiliary symbol menu, the auxiliary symbol can be added. Supplementary symbols are used as follows. Supplementary symbol "/": When the order of receiving a plurality of response test events is indefinite, the supplementary symbol "/" is used as shown in FIG. In the description example of the test sequence in FIG. 13, the auxiliary symbol “/” added to the fourth and fifth lines is
The sixth to sixth lines show that "MTABindResult" having a different connection number as the ASP parameter value may be received from any connection number. Supplementary symbol “>”: When the parameter value of the input test event is designated at the time of test execution, the supplementary 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, but if you want to change the parameter value of “Message” for each loop, “>” as shown in FIG. Is added to describe the test sequence. Therefore, the auxiliary symbol “>” on the fifth line in FIG. 14 indicates that the test execution can be interrupted on the fifth line at the time of test execution, this state can be designated by the parameter of the PDU or the parameter of ASP, and then the test execution can be restarted. Is shown. Supplementary symbol "+": The supplementary symbol "+" is used when it is desired to concatenate PDUs, and details will be described later with reference to FIG. Supplementary symbol "*": The supplementary symbol "*" is used when the same response test event is received an indefinite number of times, and the details thereof will be described later with reference to FIG. Supplementary symbol "?": The supplementary symbol "?" Is used to indicate a response test event that need not be received, and details thereof will be described later with reference to FIG.

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

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

In FIG. 15, the test event "MTABindA" which is the first line in the test sequence illustrated in FIG.
The screen side of the PDU editor 12 for the "rgument" is shown. Here, the PDU of the application layer of the OSI reference model.
Is ASN. It is defined according to the 1st definition (Abstract Syntax Notation 1) and has a set of unordered parameters (SET) and selection from multiple parameters (CHO).
It has a tree structure that combines data structures such as ICE). Therefore, as the setting of each parameter value in the PDU editor 12, for the leaf of the above tree structure,
Character strings and numerical values are input in formats such as "IA5String" and "INTEGER". For example, in the SET screen example of FIG. 15 in the PDU editor 12, “initiato
When "r-name (MTAName)" is selected, the screen shown in Fig. 16 is displayed and a character string is required to be input in the format of "IA5String." Then, the required character string is input as a parameter value. In the example screen of Fig. 15, "initiator-cred"
If you select "entials (Initiator Credientials)", the CHOICE screen shown in Fig. 17 is displayed.
It requires the selection of two data types, "(Password)" and "strong (Strong Crediential)". So, for example, "si
If you select "3ple (Password)", CHOIC in Fig. 18
The E screen is displayed, where "IA5String" and "OCT" are displayed.
It requires the selection of two data types such as "ET STRING". Then, for example, when "IA5String" is selected, the screen of Fig. 19 is displayed, and the character string is requested for the first time. Enter as a parameter value.

[Input of ASP Parameter] An example of setting ASP parameter values by the ASP editor 13 will be described with reference to FIGS. 1, 5, 7, and 20 to 22.
To enter the ASP parameter value for each test event, select the test event and activate the ASP editor 13 in the test sequence editor 11 as shown in FIG. And the hand part 40 and the display part 50
7, all the parameters of the ASP of the input test event are set, and the parameters of the ASP of the response test event are set only for those which should be judged whether they have been correctly received. In FIG. 7, when a new ASP parameter value is set, the input unit 40 edits the ASP parameter, and then save or end is designated as necessary. In saving, the input parameter value is created and saved as a file for reuse by inputting a file name. At the end, the input parameter value is saved. Also,
When using the ASP parameter values set from the beginning to the previous time, or when the A saved in the test result analysis unit 30 is used.
When using the parameter value of SP, the file of ASP parameter is called by inputting the file name etc.
A desired parameter setting is edited using the P parameter.

When the ASP editor 13 is activated, the ASP
2 for displaying the parameter value of FIG.
0 or the screen shown in FIG. 21 is displayed. The screen example of FIG. 20 is the ASP editor 1 for the test event (MTABindArgument) on the first line in the test sequence of FIG.
21 is the screen of FIG. 21, and the screen example of FIG. 21 is the test event (MTABindResul) of the second line in the test sequence of FIG.
It is a screen of the ASP editor 13 for t). Corresponding to such a screen, the input unit 40 inputs the ASP parameter and makes the setting. 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 a parameter value,
Like “acceptance”,
For those such as "ACSE rejected" and "PL user rejected" that take only limited values, a table of these parameter values is prepared in advance in the ASP editor 13 to simplify the input, and this table, that is, the menu. You can choose from. On the other hand, "CEP-I
For parameter values that can take arbitrary values, such as those related to "D", "Responding presentation address", etc., enter as many numeric values or character strings as necessary according to the data type. For simplification of input, it is possible to directly specify the value to be sent or the value to be received during the test execution.For example, in "Responding presentation address", the ASP of the first line in the test sequence of FIG. ““ RT-OPENind ”parameter“ Called prese
If you want to use the parameter value of "ntationaddress"
As shown in Fig. 22, line number 1 is added to "1.called pre
Just type "sentation address".

<Structure Operation of Test Execution Unit> FIGS. 1 and 1
1, the test execution unit 20 will be described with reference to FIGS. The test execution unit 20 uses the test scenario created by the test scenario creation unit 10 to interpret the test sequence line by line in the order of test event numbers, perform a test facing the system under test, and test the test results. The test result is saved in a file for passing to the result analysis unit 30. When the test event is the input test event, the test execution unit 20 transmits the PDU and ASP to the system under test. This transmission is basically performed after waiting for the transmission waiting time set as a fixed value in advance, but as in the input test event in 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, the transmission is performed after waiting for a time designated by the "WAIT" command, for example, 10 seconds.
On the other hand, when the test event is the response test event, the test execution unit 20 waits until the PDU and the ASP are received from the system under test, and the PDU name, the ASP name specified by the response test event, and their parameter values, The PDU name, ASP name, and their parameter values actually received are compared. If the result of the comparison indicates that they are different, the test execution is terminated. In the reception in the response test event, the timeout time is set as a fixed value, and if there is no reception by this time, it is considered that the predetermined test event has not been received.

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

Further, the test execution unit 20 can interrupt the test execution by selecting the test suspension during the test execution by the input unit 40 or the like, and can also interrupt the test execution by selecting the restart of the test. The test execution can be resumed from the test event. Also, in the case of an input test event to which the auxiliary symbol “>” is added, like the input test event in the fifth line of the test sequence of FIG. 14, the test execution unit 20 sends the input test event before transmission. 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. Due to the interruption of the test execution, the parameters of the input test event to which the auxiliary signal “>” is added are used 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. I am able to enter. When the input of the parameters is completed, the test execution is restarted from the interrupted test event by activating the restart of the test execution on the test execution screen or the like.

<Structure 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. Of the test result analysis unit 30, the test result sequence analyzer 31 mainly analyzes the sequence of events in the test result, and distinguishes the test event actually transmitted from the test event actually transmitted at the time of test execution, The (N) -PDU name and the (N-1) -ASP name are respectively displayed and recorded with the transmission / reception time and the like. FIG. 23 shows an example of the screen display. This shows the result of executing the test scenario of FIG.
The test result is displayed on the screen by the sequence analyzer 31. When analyzing the parameter values of PDU and ASP, the test result sequence analyzer 31
Then, the test event is designated and the PDU analyzer 32 and the ASP analyzer 33 are activated. The PDU analyzer 32 is the PD of the test event transmitted / received during the test execution.
The parameter value of U is analyzed, the parameter value of the analyzed PDU is displayed, and it is also saved in a file. 25 and 2
Each screen example of 6 shows a screen display of the analysis result by the PDU analyzer 32 for the test event in the first line of FIG. The ASP analyzer 33 analyzes the ASP parameter values of the test event transmitted / received during the test execution, displays the analyzed ASP parameter values, and saves them in a file. The screen example of FIG. 27 is the same as that of FIG.
The screen display of the analysis result by the ASP analyzer 33 with respect to the test event of the line is shown.

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

<Creation of SL Protocol Test Scenario> An example of preparation of an SL protocol test scenario will be described with reference to FIGS. 1, 4 to 7 and FIG. As shown in the test scenario creation flowchart of FIG. 4, at the start of test scenario creation, the test scenario creation unit 10 is instructed by the input unit 40 whether or not a new test scenario is created. When a new test scenario creation is specified, the test sequence editor 11 is activated. If not, the created test scenario name is input to call the test scenario file and the test sequence editor 11 is activated. Test sequence editor 11
When is started, according to the flowchart shown in Fig. 5,
The description of the test event for the test sequence, the selection of cut, copy, paste, etc. for the 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 end, etc. are designated. 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 section 40 and a display section 50 as shown in FIG. 1, and as shown in the description example shown in FIG. In addition, test events (response events) to be received by the test apparatus from the system under test are divided into response fields, and the input events are input in the input section 40 to describe the test events in order and record them 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 having no SPDU name of the same protocol such as ONNECTreq "is transmitted / received, the T-ASP name is described.

In the description example of FIG. 29, the test apparatus is "T-CON".
This is an example of a test sequence in the case of requesting establishment of a connection by transmitting "NECTreq" to the system under test.
It is also possible to describe a test sequence that requests establishment of a connection by sending "CONNECTind" to the test apparatus.

The test event can be described by selecting it from the 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 each SPDU name of the SL protocol, each T-ASP name, and an appropriate sequence control command for controlling the test sequence. For example, the "WAIT" command indicates to wait the specified number of seconds before processing the next test event. Therefore, the description example of FIG. 29 is a test sequence for transmitting “MIA” three times every 10 seconds.

Further, an auxiliary symbol can be added to each test event in order to operate in association with a subsequent test event. Therefore, the test sequence editor 11 has a file of the supplementary symbol menu as shown in FIG. 12, which is displayed on the screen of the display unit 50.
Then, the test event is designated, and the auxiliary symbol to be added is selected from the auxiliary symbol menu as described above to add the auxiliary symbol. The auxiliary symbol “+” added to each test event on the 5th, 8th, 10th and 15th lines of 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 concatenated to form one T-ASP called "T-DATAreq".
Means to carry in. In addition, the auxiliary symbol “*” added to the test event in the seventh line of 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 on the seventh line in FIG. 29,
This means that the SPUD of "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 designated 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 may be performed without interruption. However, if the immediately following line is a response test event, such as the auxiliary symbol “?” On the seventh line in the description example of the test sequence in FIG. 30, the next 8 in the waiting state for “DT” on the seventh line. When "MIP" on the line is received,
The "DT" on the 7th line means that it has not been received, and means to move to the test execution of the test event on the 9th line. Here, the description example of FIG. 30 is a test sequence when the system under test requests connection establishment by transmitting "T-CONNECTind" to the test apparatus.

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

[Input of SPDU Parameter] The setting of the SPDU parameter value by the PDU editor 12 will be described with reference to FIGS. 1, 5, 6, 31 and 32.
To enter the SPDU parameter value for each test event of the SL protocol, select the test event and, as shown in FIG. 5, test sequence editor 1
In step 1, the PDU editor 12 is activated. Then, by using the manual force unit 40 and the display unit 50, it is determined whether all the parameters of the SPDU of the input test event are set and the parameters of the SPDU of the response test event are correctly received according to the flow shown in FIG. Set only for what should be done. In FIG. 6, in the case of newly setting the parameter value of the SPDU, the PDU parameter is edited by the input unit 40, and thereafter, saving and ending are designated as necessary. In saving, the input parameter value is encoded, and a file for reuse is created and saved by inputting a file name. At the end, the input parameter value is encoded and saved. Also,
When using the parameter value of the SPDU set from the beginning to before, 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,
A desired parameter setting is edited using the decoded PDU parameter.

FIG. 31 shows 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. Further, in FIG. 32, the test event “D
A screen display example of the PDU editor 12 for T "is shown. By the way, when a communication protocol conformance test of a lower layer in the OSI reference model is performed like the session layer SL, a protocol of a higher layer than that is used. Therefore, the upper layer PDU carried as user data is separately created by a PDU editor for the upper layer (presentation layer PL for SL) and saved as a user data file. Then, in SL, the user data file is divided and transmitted by the PDU editor 12. In order to have a function of dividing and transmitting such a user data file, as shown in FIG. In the PDU editor 12 for PDUs containing user data, specify the user data file User data fail), the top address (User data offset) to be cut out, and the number of bytes (User data bytes) to be cut out can be set.The editor for the upper layer PDU for creating and saving the user data file Test sequence editor 11
It can be selected and started 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, 7 and 33. In order to input the T-ASP parameter value for each test event, the test event is selected and the ASP editor 13 is activated in the test sequence editor 11 as shown in FIG. And the hand part 40 and the display part 50
7, all the T-ASP parameters of the input test event are set by the flow shown in FIG. 7, and the T-ASP parameters of the response test event are set only for those for which it is determined whether or not they are correctly received. To do. Figure 7
In the case of setting a new ASP parameter value, the ASP parameter is edited by the input unit 40, and then save or end is designated as necessary. In saving, the input parameter value is created and saved as a file for reuse by inputting a file name. At the end, the input parameter value is saved.
Further, when using the T-ASP parameter values set from the beginning to before, or when using the T-ASP parameter values stored in the test result analysis unit 30,
The ASP parameter file is called by inputting a file name, etc., and desired parameter settings are edited using the ASP parameter.

When the ASP editor 13 is started, the ASP
In order to set the parameter values of FIG.
The screen shown in 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.
It is a screen of 3. Corresponding to such a screen, the input unit 4
With 0, the ASP parameter is input and setting is performed. For parameter values that take only limited values, a table of these parameter values is prepared in advance in the ASP editor 13 in order to simplify the input, and the table 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, the required number of numerical values and character strings are input as they are according to the data type. Further, as the parameter value, the value to be transmitted or the value to be received during the test execution can be specified as it is for the simplification of input.

<Structure Operation of Test Execution Unit> FIGS. 1 and 29
The test execution unit 20 will be described based on FIG. 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 line by line in the order of test event numbers, perform a test facing the system under test, and perform the test. The result is saved in a file for passing to the test result analysis unit 30. If the test event is an input test event,
The test execution section 20 transmits the SPDU and T-ASP to the system under test. This transmission is basically performed after waiting for the transmission standby time set as a fixed value in advance, but as in the input test event on the 17th line 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 designated by the "WAIT" command, for example, 20 seconds. On the other hand, when the test event is the response test event, the test execution unit 20 waits until the SPDU and the T-ASP are received from the system under test, and then the SPDU name, the T-ASP name specified by the response test event, and further those Parameter value, SPDU name actually received, T-ASP
Names, and their parameter values. As a result of the comparison,
If they are different, the test execution is to be terminated.
In the reception in the response test event, the timeout time is set as a fixed value, and if there is no reception by this time, it is considered that the predetermined test event has not been received.

Further, the test execution unit 20 displays the test events of the SL protocol transmitted and received during the test execution in the same format as the test sequence with the transmission and reception time.
It is designed to be displayed on the screen. Also, the test execution unit 2
0 indicates that the test events transmitted / received, the parameter values of those SPDU and T-ASP, and the transmission / reception time are saved in a file.

Furthermore, the test execution unit 20 can interrupt the test execution by selecting the test suspension during the test execution by the input unit 40 or the like, and can also interrupt the test execution by selecting the restart of the test. The test execution can be resumed from the test event. Also, in the case of the SL protocol as well, in the case of an input test event to which the auxiliary symbol “>” is added like the input test event in the SL protocol, 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 activated. By suspending the test execution, the parameter of the input test event to which the auxiliary signal “>” is added can be input newly or by using the PDU parameter value or the ASP parameter value in the test result executed halfway. I have to. When the input of the parameters is completed, the test execution is restarted from the interrupted test event by activating the restart of the test execution on the test execution screen or the like.

<Structure Operation of Test Result Analysis Unit> Next, the test result analysis unit 30 will be described. In the test result analysis unit 30 of the SL protocol, the test result sequence analyzer 31 mainly analyzes the sequence of events in the test result, and detects the test event actually transmitted and the test event actually received during the test execution. The SPDU name and the T-ASP name are classified, and the transmission / reception time and the like are attached to each for display or recording. Also, SPDU
When analyzing the parameter values of T-ASP and T-ASP, the test result sequence analyzer 31 specifies a test event and activates 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 / received during the test execution, 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 / received during the test execution, displays the analyzed T-ASP parameter values, and saves them in a file.

Although the above-mentioned embodiment is concerned with the conformity test of each protocol of the application layer and the session layer of the OSI reference model, the invention is not limited to this, and the conformity test of other Nth layer protocols is also the same. The present invention can be applied to.

[0048]

According to the first aspect of the present invention, the description of the test sequence, the setting of the parameter of the PDU, and the setting of the parameter of the ASP are performed independently to create a test scenario, and a test is performed based on the created test scenario. And analyze the test results. In this way, by setting the test sequence, the parameter of the PDU, and the parameter of the ASP independently, the description of the test sequence is simplified and the setting of each parameter of the PDU and the ASP can be freely performed. It can be done, and thus test scenarios can be created in a short time. In the invention of claim 2, a test sequence editor, a PDU editor, and an ASP editor are used to create a test scenario.
Use one tool. Then, in the test sequence editor, if there is an (N) -PDU to be transmitted and received, the (N) -PDU name is used, and if the (N) -PDU does not exist, the (N-1) -ASP name is used and the test event Only the test sequence is described separately for sending and receiving, and the PDU editor specifies the test event in the test sequence and sets the (N) -PDU parameter, and the ASP editor tests for the test sequence. Specify the event and set the parameters of the lower (N-1) -ASP. In this case, the test sequence is the (N) -PDU name and (N-1) -ASP of the test event.
Writing only by name simplifies the description of the test sequence. According to the invention of claim 3, the test sequence structure can be clarified by separately describing the test event (input) to be transmitted and the test event (response) to be received, and the description can be performed easily. The test sequence can be described by selecting the (N) -PDU name and the (N-1) -ASP name from the menu. This further simplifies the test sequence description. In the invention of claim 4, the PDU editor and the ASP editor can be started by the test sequence editor to set the parameters of (N) -PDU and (N-1) -ASP, and the setting of these parameters can be easily performed. It can be carried out. In the invention of claim 5, the (N) -PDU name, (N-1) -ASP name and their parameter values stored in the created test scenario or as the test result are used in PDU units and ASP units. Then, setting of (N) -PDU parameters and (N-
1) -ASP parameters can be set, and test scenario creation becomes easier. 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.

[Brief description of drawings]

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

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

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

FIG. 4 is a diagram showing a schematic flow of test scenario creation 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 view showing a screen display example 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 diagram 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 P editor.

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

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

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

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

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

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

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

FIG. 28 is a diagram showing a test outline of the 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 diagram showing an example of a screen in a PDU editor for SL protocol.

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

FIG. 33 is a diagram showing a screen display example in the 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

 ─────────────────────────────────────────────────── ─── Continuation of the front page (72) Inventor Kenji Suzuki 2-3-2 Nishishinjuku, Shinjuku-ku, Tokyo International Telegraph and Telephone Corporation

Claims (6)

[Claims] 1. A device for testing conformity of (N) -protocol of a system implementing layer N of the OSI reference model, wherein a description of a test sequence, which is the sequence of input and response test events, and parameters of a PDU. Of the test sequence according to the setting independent of the description of the test sequence and the setting independent of the description of the test sequence of the lower ASP parameters, and a test scenario creating means for creating a test scenario based on the created test scenario. And a test result analyzing means for analyzing a test result, and a communication protocol compatibility testing device. 2. The test scenario creating means, when there are (N) -PDUs to be transmitted and received, (N) -PDUs.
If the same (N) -PDU does not exist, (N-
1) -Specify the test sequence editor that describes only the test sequence and the test event in the test sequence by dividing the test event into one that sends the test event and one that receives the test event (N)
-Specify the PDU editor that sets the PDU parameters and the test event in the test sequence (N-
1) -The ASP editor which sets the parameter of ASP, It is provided, The communication protocol compatibility test apparatus of Claim 1 characterized by the above-mentioned. 3. The test sequence editor can select (N) -PDU name or (N-1) from a preset menu.
-The communication protocol compatibility test apparatus according to claim 2, which has a function of selecting an ASP name. 4. The test sequence editor is the P
3. The communication protocol compatibility test apparatus according to claim 2, which has a function of activating a DU editor and the ASP editor. 5. The PDU editor and the ASP editor are respectively (N) -PDU name, (N) stored in a created test scenario or as a test result.
-1) -Specify the ASP names and their parameter values in the PDU
3. The communication protocol compatibility test apparatus according to claim 2, which has a function to be used in units and ASP units. 6. The communication protocol compatibility test apparatus according to claim 1, wherein the scenario creating means has a function of using the created test scenario for creating another test scenario.