JPH01136496A - Verification route automatic selection system - Google Patents

Abstract

PURPOSE:To improve the efficiency of selection of verification route and execution job by comparing an instance data outputted from a simulation means with an instance data representing simulatingly the same state stored already in a task module simulate data storage means so as to detect the presence of the instance data after storage. CONSTITUTION:A comparator means 400 compares an instance data outputting a simulation means 100 with an instance data representing simulatingly the same state stored already in the task module simulate data storage means 200. When the instance data coincident and stored already is detected, the storage of the instance data outputted from the simulation means 100 to the storage means 200 is stopped. If the coincident said data is not detected, the instance data is stored in the storage means 200. Thus, all verification routes required to verify the task module are selected automatically and the verification processing is executed, the labor required for the selection and execution of the verification route is much reduced.

Description

[Detailed Description of the Invention] [Summary] This invention relates to an automatic task module verification system, and in particular to an automatic verification route selection method for verifying a task module that controls the operation of an exchange using a simulation model. In order to make the settings as efficient as possible, the task module that controls the operation of the exchange is input.
A simulation means for outputting instance data that pseudo-indicates the state of the exchange as a result of executing the task module, a task module simulation data holding means for holding the instance data output by the simulation means, and a task module simulation data holding means In the task module automatic verification system, the task module automatic verification system includes a verification means for performing verification of the task module based on the instance data held by the task module, the instance data output by the simulation means is transferred to the same The state is compared with instance data that pseudo-indicates the state, and if matching retained instance data is detected, the instance data output from the simulation means is stopped being retained in the task module simulation data retaining means, and a match is detected. The present invention is configured to provide a comparison means for causing the task module simulation data holding means to hold the instance data output from the simulation means when the held instance data is not detected.

[Industrial application field]

The present invention relates to an automatic verification route selection method in an automatic task module verification system that verifies task modules constituting a call processing program that controls the operation of an exchange using a simulation model.

A storage program control switching system provides various switching services by having a central controller execute various service modules that constitute a call processing program.

Therefore, it is essential to eliminate errors when creating the service modules that make up the call processing program and the task modules that make up the service modules.

In order to reduce the effort required to detect errors in such a task module as much as possible, the task module is executed using a simulation model that simulates the operation of an actual exchange, and an instance that pseudo-presents the status of the exchange as a result of execution. An automatic task module verification system that verifies task modules based on data has been put into practical use.

[Conventional technology]

FIG. 4 is a diagram showing an example of a task module to which the present invention is applied, and FIG. 5 is a diagram showing an example of a conventional task module automatic verification system.

In FIG. 4, the STI assigns 1, 2, 3 and 4 as captured terminal device numbers to extensions A, B and C accommodated in the automatic private branch exchange and to the held sound source H, respectively, and to This is a state number given to a state in which a mutual communication path is set between 0 and 0, and a communication path from the held sound source H to extension A is set. (Hereafter, state number STI
The state in which this is given is called the state STI. ) In such state STl, extension C hangs up the telephone (
When the on-footer) event LNON (C) occurs,
A predetermined task module TM1 is executed and transitions to state ST4.

State ST4 indicates a state (1) in which the communication path from the held sound source H to extension A is set, the communication path between extensions B and C is released, and the timer is activated.

In this state ST4, when an event CTOO in which the activated timer times out occurs, task macro %C sets a communication path from captured terminal device number 2 to 1.
MODS C2, CI, task macro for setting the communication path from captured terminal device number 1 to 2 %CMODS C
1, C2, and a task macro % indicating the end of execution of the task module are set, and the state transitions to state 5 in which the communication path from the held sound source H to the extension A is released.

Note that state ST4 is also transitioned from other states BsT2 and Sr1 of state STI by executing predetermined task modules TM2 and 7M3 due to the occurrence of event LNON (C).

State ST4 transitioned from such states ST2 and ST3
For example, when transitioning from state aST2, the state is such that a communication path from the held sound source H to extension B is set, the communication path between extensions A and C is released, and the timer is activated (1 ), etc., the state ST that has transitioned from the state STI.
4 and the setting state of the communication path, etc. do not necessarily match completely, but in both cases, upon occurrence of event CTOO, task module TM4 is executed and transitions to state ST5.

Therefore, in order to verify task module TM4, it is necessary not only to verify the execution process of task module TM4 using state ST4 that has transitioned from state STI as the transition source state, but also to verify the execution process of task module TM4 that has transitioned from state fisT2 or state BST3.
It becomes necessary to verify the execution process of the task module TM4 with TM4 as the transition source state.

The task module automatic verification system shown in FIG. 5 executes the above task module on a simulation model that simulates an actual exchange, and verifies the task module based on the execution result.

In FIG. 5, task modules to be executed on a simulation model are input and stored in the task module section 1 from, for example, a keyboard (not shown).

The task module reading section 2 extracts the task module stored in the task module section l, converts it into internal data, and stores it in the task module internal data conversion holding section 3.

The simulation unit 4 sequentially extracts the task macros that constitute the task module converted into internal data stored in the task module internal data conversion holding unit 3, and extracts the instance data already held in the task module simulation data holding unit 5. A predetermined change corresponding to the task macro is made to create instance data for a new state, and the instance data is stored in the task module simulation data holding unit 5.

The verification unit 6 is the task module internal data conversion holding unit 3
The task module verification process is executed by referring to the task macro extracted from the task module and the instance data stored in the task module internal data conversion and storage unit 3.

With this task module automatic verification system, the fourth
In order to verify the task module TM4 shown in the figure, first the task module simulation data holding unit 5
From the state where the instance data corresponding to the state STI has been accumulated, the event LNON (C) and the required task module TM1 are manually input to the task module department,
The simulation unit 4 executes a simulation of the occurrence of the event LNON (C) and the execution of the task module TM1, creates instance data corresponding to state 11sT4 and stores it in the task module simulation data holding unit 5, and then TM4 is input to the task module section 1 and verification is performed through the above-described process.

Next, from the state where the instance data corresponding to state ST2 has been accumulated in the task module simulation data holding section 5, the simulation section 4 executes a simulation of the occurrence of the event LNON (C) and the execution of the task module TM2, and the state ST4 is reached. Instance data corresponding to is created and stored in the task module simulation data holding section 5, and then the task module TM4 is input to the task module section 1 and verification is executed by the above-described process.

Finally, while the instance data I corresponding to the state MST3 is stored in the task module simulation data holding section 5, the simulation section 4 executes a simulation of the occurrence of the event LNON (C) and the execution of the task module TM3. Instance data corresponding to is created and stored in the task module simulation data holding section 5, and then the task module TM4 is input to the task module section 1 and verification is performed by the above-described process.

Note that state ST4 transitioned from state ST2 and state ST3
Assuming that the instance data is the same as that of the state ST4 to which the state transitioned from, the time required for the verification process can be reduced by omitting the verification starting from the state ST3.

[Problem that the invention seeks to solve]

As is clear from the above explanation, in a conventional task module automatic verification system, in order to verify task module TM4, for example, the state STI to state ST
4, a verification route that verifies task module TM4 after transitioning from state ST2 to state ST4, and a verification route that verifies task module TM4 after transitioning from state ST3 to state ST4. Verification routes must be selected by the verifier and executed independently, and verification routes that have the same conditions (for example, a verification route that transitions from state ST3 to a verification route that transitions from state ST2) are omitted. In order to improve efficiency, there is a problem in that a lot of effort is required to select and execute a verification route for the task module TM4 to be verified.

An object of the present invention is to make the selection and execution of a verification route necessary for verifying a task module as efficient as possible.

[Means for solving problems]

FIG. 1 is a diagram showing the principle of the present invention.

In FIG. 1, 100 is a simulation means, 20
0 is task module simulation data holding means, 3
00 is a verification means.

400 is a comparison means provided according to the present invention.

[Effect]

The simulation means 100 is configured to manually execute a task module that controls the operation of the exchange, and outputs instance data that pseudo-indicates the state of the exchange as a result of executing the task module.

The task module simulation data holding means 200 holds instance data output by the simulation means 100.

The verification means 300 performs verification of the task module based on the instance data held by the task module simulation data holding means 200.

The comparison means 400 compares the instance data output by the simulation means 100 with instance data that pseudo-indicates the same state held in the task module simulation data holding means 200, and detects matching held instance data. When the task module simulation data holding means 20 of the instance data output from the simulation means 100
If holding the instance data to 0 is stopped and matching held instance data is not detected, the instance data output from the simulation means 100 is held in the task module simulation data holding means 200.

Therefore, all verification routes necessary for verification of a task module are automatically selected and verification processing is executed, so that the labor required for selection and execution of verification routes is significantly reduced.

〔Example〕

An embodiment of the present invention will be described below with reference to the drawings.

FIG. 2 is a diagram showing a task module automatic verification system according to an embodiment of the present invention, and FIG. 3 is a diagram illustrating the instance data generation process in FIG. 2. Note that the same reference numerals refer to the same objects throughout the plan. The target task module is as shown in FIG.

In FIG. 2, a simulation section 4 is provided as the simulation means 100 in FIG.
A task module simulation data holding unit 5 is provided as the task module simulation data holding unit 200 in the figure, a verification unit 6 is provided as the verification unit 300 in FIG. 1, and a comparison unit 400 in FIG.
As such, an instance data comparison processing section 7 is provided.

The instance data comparison processing section 7 includes a comparison data item holding section 71 and an instance data comparison section 72. The comparison data item holding section 71 stores items constituting the instance data, such as the call path setting state and the captured terminal. It holds items to be compared when selecting a verification route from among the device number, timer status, captured terminal control processor status, etc.

In addition, in Fig. 3, each instance data is shown as
It is represented by a state diagram.

In FIGS. 2 to 4, the state ST shown in FIG.
When performing verification of task module TM4 whose transition source state is state ST4 that is transitioned from I to ST3,
Status S is set in the task module simulation data holding unit 5.
Event LNON (C) and task module necessary for transitioning from state fisT1 to state ST4 in a state where instance data 11 to ■3 corresponding to TI to ST3 are accumulated and instance data corresponding to state ST4 is not accumulated. When TM14 is automatically input to the task module section 1 by a means not shown, the simulation section 4 generates the instance data 141 through the process described above, and the instance data I41 and the state number ST4 to which the instance data I41 is to be assigned are generated. It is transmitted to the data comparison processing section 7.

In the instance data comparison processing section 7, the instance data comparison section 72 searches the task module simulation data holding section 5 using the state number ST4 transmitted from the simulation section 4, but currently the state number ST is
Since the instance data assigned T4 is not retained, the instance data 141 transmitted from the simulation unit 4 is assigned a state number ST4 and stored in the task module simulation data retention unit 5.

In this state, the task module section 1 receives an event) CTO.
When O and the task module TM4 are input by means not shown, the simulation unit 4 generates the instance data I411 by simulating the occurrence of the event CTOO for the instance data 141 through the same process as described above, and Instance data I412 is generated by simulating the execution of task macros %CMODS C2 and C1 that constitute module TM4, and instance data ■5 is further generated by simulating the execution of task macros %CMODS C1°C2 and %TSKFL. Then, the instance data 411 and I412 are transmitted to the instance data comparison unit 72 without assigning a status number, and the instance data I5 is transmitted to the instance data comparison unit 72 with a status number ST5 assigned.
2.

The instance data comparison unit 72 performs a task module simulation on instance data 1411 and I412 to which no state number is assigned, and instance data I5 assigned a state number ST5 that is not stored in the task module simulation data holding unit 5. The stored data is stored in the data holding unit 5.

The verification unit 6 converts the task macro extracted from the task module internal data conversion holding unit 3 into internal data as described above, and the task module simulation data holding unit 5.
Instance data I411, I412,
Verification processing is performed on I5, and it is displayed that there is no error.

Task module L based on instance data 141
! When the verification process of TM4 is completed, the state number ST is stored in the task module simulation data holding unit 5.
I41 is held as instance data assigned 4.

In this state, when the event LNON (C) and the task module TM24 necessary for transitioning from state ST2 to state ST4 are automatically input to the task module section 1 by means not shown, the simulation section 4 performs the above-mentioned process. Through the process, instance data I42 is generated and transmitted to the instance data comparison processing section 7 together with the state number ST4 to which the instance data I42 is to be assigned.

In the instance data comparison processing section 7, the instance data comparison section 72 searches the task module simulation data holding section 5 using the state number ST4 transmitted from the simulation section 4, and finds the instance data I41 assigned the state number ST4. When it is detected that the instance data 141 is retained, the comparison item set in the comparison data item holding unit 71 is extracted, and then the comparison item set in the comparison data item storage unit 71 is
For example, the instance data 142 transmitted from the simulation unit 4 and the instance data 14 extracted from the task module simulation data holding unit 5 for each call path setting state, captured terminal device number, and timer state.
Compare with 1.

As a result of the comparison, the instance data 142 matches I41 regarding the captured terminal device number and the timer state, but the instance data I4 matches the channel setting state.
Instance data 142 is different from instance data 141 because instance data 141 has a call path set from held sound source H to extension A, whereas instance data I41 has a call path set from held sound source H to extension A. This is detected and stored in the task module simulation data holding unit 5 with a state number ST4 assigned thereto.

In this state, the event CTO is sent to the task module section 1.
When O and task module TM4 are automatically input by means not shown, the simulation unit 4 generates instance data I421 by simulating the occurrence of event CTOO for instance data I42 through the same process as described above. and task module TM
Task macro %CMODS C2, CI that constitutes 4
instance data I42 by simulating the execution of
2 is generated and transmitted to the instance data comparison unit 72 without assigning a state number.

The instance data comparison unit 72 stores both instance data 411 and I 412, to which no state number is assigned, in the task module simulation data holding unit 5.

The verification unit 6 converts the task macro extracted from the task module internal data conversion holding unit 3 into internal data as described above, and the task module simulation data holding unit 5.
Verification processing is performed on the instance data accumulated in .

The verification unit 6 checks the pre-held verification rules to determine if the hold tone delivered from the hold sound source H to extension B leaks to extension A for a call path setting state such as instance data ■422. Output the verification results.

Task module T based on instance data 142
When the verification process for M4 is completed, 141 and I4 are stored in the task module simulation data holding unit 5 as instance data assigned the state number ST4.
2 is retained.

In this state, when the event LNON (C) and the task module TM34 necessary for transitioning from state ST3 to state ST4 are automatically input to the task module section 1 by means not shown, the simulation section 4 performs the above-mentioned process. Through the process, instance data I43 is generated and transmitted to the instance data comparison processing unit 7 together with the state number ST4 to which the instance data I43 is to be assigned.

In the instance data comparison processing section 7, the instance data comparison section 72 searches the task module simulation data holding section 5 using the state number ST4 transmitted from the simulation section 4, and searches the instance data 141 and the instance data assigned the state number ST4. 142 is held, first extracts the instance data 141, and then extracts the instance data 141 for each comparison item (call path setting state, captured terminal device number, and timer state) set in the comparison data item holding section 71. The instance data I43 transmitted from the simulation unit 4 and the instance data I41 extracted from the task module simulation data holding unit 5 are compared.

As a result of the comparison, the instance data 143 is the same as the instance data 1 regarding the captured terminal device number and timer status.
41, but it is detected that the instance data 143 is different from the instance data 141 regarding the call path setting state, and then after extracting the instance data 142, the comparison item set in the comparison data item holding unit 71 is Instance data I43 transmitted from the simulation unit 4 and instance data 142 extracted from the task module simulation data holding unit 5 for each (call path setting state, captured terminal device number, and timer state)
Compare with.

As a result of the comparison, if it is detected that the instance data 143 matches 142 for all comparison items (call path setting state, captured terminal device number, and timer state), the task module simulate data retention of the instance data 143 is performed. The storage in section 5 is stopped.

Therefore, the verification unit 6 does not perform verification processing of the task module TM4 based on the instance data I43, which is equivalent to verification processing of the task module TM4 based on the verified instance data T42.

As is clear from the above description, according to the present embodiment, the instance data comparison processing unit 7 selects the instance data 141 to 143 that are given the same state number ST4.
The instance data 143 that is equal to the instance data I42 with respect to the comparison items set in the comparison data item holding unit 71 is prevented from being stored redundantly in the task module simulation data holding unit 5, and as a result,
It prevents the same verification process from being executed redundantly, automatically sets the required verification route, that is, the instance data I41 and 142, and automatically performs the verification process of the task module TM4.

It should be noted that FIGS. 2 to 4 are only one embodiment of the present invention, and for example, the verification target is not limited to the task module TM4 (the verification process may be executed in batch for each service module). Although many other modifications may be considered, the effects of the present invention remain the same in any case.

〔Effect of the invention〕

As described above, according to the present invention, in the task module automatic verification system, all verification routes necessary for verification of a task module are automatically selected and verification processing is executed. The labor required for the work is significantly reduced.

[Brief explanation of the drawing]

FIG. 1 is a diagram showing the principle of the present invention, FIG. 2 is a diagram showing a task module automatic verification system according to an embodiment of the present invention, FIG. 3 is a diagram illustrating the instance data generation process in FIG. FIG. 4 is a diagram showing an example of a task module to which the present invention is applied, and FIG. 5 is a diagram showing an example of a conventional task module automatic verification system. In the figure, 1 is a task module section, 2 is a task module reading section, 3 is a task module internal data conversion holding section, 4 is a simulation section, 5 is a task module simulation data holding section, 6 is a verification section, and 7 is instance data a comparison processing unit; 71 is a comparison data item holding unit;
72 is an instance data comparison unit, 100 is a simulation means, 200 is a task module simulation data holding means, 300 is a verification means, 400 is a comparison means,
fP, Inventive Star Chart No. 1 g

Claims (1)

[Claims] A task module for controlling the operation of an exchange is input;
simulation means (100) for outputting instance data that pseudo-indicates the state of the exchange as a result of executing the task module; and task module simulation data holding means for holding the instance data output by the simulation means (100). (200)
and verification means (300) for verifying the task module based on the instance data held by the task module simulation data holding means (200).
), wherein the instance data output by the simulation means (100) is replaced with instance data that pseudo-indicates the same state held in the task module simulation data holding means (200). If matching held instance data is detected, the holding of the instance data output from the simulation means (100) in the task module simulation data holding means (200) is stopped, and a match is detected. further comprising a comparison means (400) for causing the task module simulation data holding means (200) to hold the instance data output from the simulation means (100) when the held instance data is not detected. Features automatic verification route selection method.