JP2854957B2 - Initial setting of call processing - Google Patents

Description

Description: TECHNICAL FIELD The present invention relates to an initial setting method for call processing of an electronic exchange. More specifically, the present invention relates to a method for initializing call processing when a failure occurs due to hardware or other causes in an electronic converter.

(Description of Prior Art) With the diversification of telecommunication services, electronic switches have been required to have higher functions. Conventionally, a program for controlling an electronic exchange comprises a set of "commands" describing the operation of the exchange and a set of "data" necessary for the instructions or operations.

Normally, when the system is restarted or when a specific call is initialized, a restart processing program is started. This restart processing program manages the initial setting data of the call processing program for each restart level, and performs the initial setting according to the data initial setting condition.

(Problems to be Solved by the Invention) However, in the conventional method, each time a call processing program corresponding to a new system is created, it is necessary to newly create a restart processing program. Also added functions to call processing,
When there is a change, deletion, etc., the restart processing program must be updated each time, and there is a problem that it takes time and effort.

On the other hand, the concept of so-called object-oriented programming has been recently proposed for the purpose of improving software productivity. That is, data representing information of a target function,
The operation of the data is encapsulated integrally, and this capsule is called an object. The object is externally recognized as a software entity that performs a desired operation when a predetermined message is sent.

(Object of the Invention) The present invention employs an object-oriented concept for control of an electronic exchange, allows easy design and modification of functions in an initial setting method of the electronic exchange, and provides an initial environment capable of providing a good execution environment to application software. The purpose is to provide a setting method.

(Means for Solving the Problems) According to the present invention, in an initial setting method of an electronic exchange in which an actual object exists on software corresponding to each component of the electronic exchange, each object generates an association, The electronic exchange by operating the electronic exchange by joining and leaving the association, destroying the association when the system is restarted, and initializing the objects participating in the association. The setting method.

(Operation) The electronic exchange has objects that are software entities corresponding to the respective components. This object performs a predetermined operation when receiving a message from another object.

The electronic exchange also has a function of managing a plurality of these objects as one unit.

The object generates an association, which is an initial setting unit. An object can also participate in and leave associations created by other objects.

Here, if an abnormality occurs in the system for some reason, the system starts an initial setting operation. When the initialization operation is started, the electronic exchange destroys the association. Upon the destruction of the association, the objects participating in the association are initialized.

Each object can also freeze the association so that it is not initialized on system restart. The electronic exchange does not initialize the objects participating in the frozen association when the system is restarted.

With this configuration, the initial setting of the object can be easily controlled.

(Embodiment) FIG. 1 is a conceptual diagram showing the position in the exchange software of the present invention.

The present invention is a method for initializing an electronic exchange operating on computer hardware 100.

The program existing on the computer hardware 100 controls and gives instructions to the electronic exchange hardware 101 to operate it. The electronic exchange 101 has outgoing lines, incoming lines,
The system is composed of many types and many resources such as various trunks, subscriber circuits, time division switches, and communication paths.

First, an OS 102 exists as a program for controlling the electronic converter 101. OS 102 is the most basic part of software. An execution management hierarchy 103 exists as an upper hierarchy of the OS 102. The execution management layer 103 manages and controls the execution of an application program described later. An application program 104 exists as an upper layer of the execution management layer 103. The application program 104 can be understood as a collection of a large number of objects that include an instruction for causing the electronic converter 101 to perform various operations and data necessary for executing the instruction as an integrated capsule. In order to execute an application program which is a set of objects, the execution management hierarchy 103 includes an object control information area OCB for managing attributes of each object, a current state, and the like, an association management area ACB for managing an association composed of a plurality of objects, A thread management area SCB for managing a thread composed of a plurality of objects executed at the same time is included.

In FIG. 1, the OS 102 and the execution management hierarchy 103 control and manage application software and objects,
An object infrastructure that provides an execution environment in which application software operates is called an object infrastructure. In other words, an object infrastructure is a program that controls the creation and destruction of objects described in an application program, and that implements message communication between objects. The software that gives.

FIG. 2 shows the concept of the objects constituting the application program.

In the exchange software 201 that takes an object structure,
Each element of the switching system (eg, individual outgoing lines, incoming lines,
Service transformers, speech paths, subscriber lines, etc.) all exist as individual objects. These objects encapsulate data necessary for the operation of each element and a series of processes that handle the data.For example, OGT objects send messages such as calling, sending numbers, and starting a call. The predetermined operation is executed only by the above operation.

The objects include a caller object 202, a called party object 203, which is generated each time a call is made, and a call control object 204 which is a center of a series of processes from a call to an incoming call. There is. For each telephone call, the required riot, i.e., the allocation, control and release of objects, takes place and the exchange connection proceeds. Each object independently performs an operation for realizing the function of the object, and generates an association as necessary. An association which is a feature of the present invention will be described with reference to FIG.

An association is composed of one or a plurality of objects, and serves as one initial setting unit. An association is a unit on software for managing a plurality of objects that are functionally related to each other when a program is executed as a group.
The association is made with the application program 104
When an association generation message is sent from an object in the execution management hierarchy 103 to the execution management hierarchy 103, it is generated in the execution management hierarchy 103.

Each object can create a new association as needed. Each object is
Can participate in associations created by other objects. An object that has participated in a certain association is handled from the execution management hierarchy 103 in the same manner as other objects that have participated in the association. An object joins the association by sending a join message for the association. When an object sends a message to participate in an association, the object specifies an initialization method when the association is destroyed. Fig. 3 (a)
In the figure, a state is shown in which the object A301 generates an association, and the object # 302 and the object Y303 are participating in the association. Each object can also unsubscribe from the association. When an object withdraws from the association, the object is thereafter handled from the execution management layer 103 independently of other objects. The object unsubscribes from the association by sending an unsubscribe message to the association. The association once created disappears when all the objects participating in the association have withdrawn.

As shown in FIG. 3 (b), the association is destroyed when a destroy message is received from the object that created the association. The destruction of the association triggers the initialization of the objects currently participating in the association. That is,
When the association is destroyed, the objects participating in the association are forcibly terminated or receive an initialization message according to the initialization method specified at the time of the association participation. FIG. 3B shows an example in which the object # 302 is terminated and the object Y303 receives an initialization message. At this time, the object Y303 that has received the initialization message starts an initialization procedure included in the object.

Each object can also freeze the association. Frozen associations are not destroyed in the event of a system failure.
As a result, the objects participating in this association are not initialized.

By freezing the association in this way,
Processing continues without interruption. If this association is an object involved in call processing, the call is not interrupted, and so-called "call rescue" can be performed. In addition,
Each object can specify whether or not a repair message is required at the end of the resumption process at the time of joining the association. A restoration message is sent to the object for which the restoration message "necessary" is designated at the end of the resuming process, and the object that has not been initialized can be restored to a normal state.

The management from the generation of the association to the disappearance of the association described above is performed by the object infrastructure, that is, the OS 102 shown in FIG.
And the execution management hierarchy 103. The structure and function of the execution management hierarchy 103 will be described with reference to FIG. The application program 104 is an object A
401, object # 402 and object Y403. The object A401 generates an association A404, and the object Χ402 and the object Y403 are
Participating in this Association A. Work management hierarchy
In 103, other associations B and C may be created. The execution management hierarchy 103 has an association management area ACB therein. When the execution management hierarchy 103 receives an association generation message from an object, the association management area includes an identification number of the generated association A, an identification number of the object that generated the association,
The identification numbers of the objects participating in the association and their initial setting methods are registered.

The execution management hierarchy 103 has an object control information area OCB corresponding to each object existing in the application program. In the object control information area OCB, information such as the identification number of the association in which the object is currently participating, the initial setting method specified at the time of the association participation, the necessity of a repair message, and the like are registered.

When the execution management layer 103 receives an association freeze message from the object, the execution management hierarchy 103 registers that the association is frozen in the association management area ACB. When the system resumes at phase 1 level (resuming call relief)
The execution management layer 103 refers to the association management area ACB and determines whether or not each association is frozen. In the object control information area OCB corresponding to the object participating in the association determined to be frozen, it is registered that the object is a “non-initialized object” which is not a target of the initial setting. Therefore, when the system is restarted, these "non-initialized objects" are not initialized.

Next, a specific call initial setting method to which the present invention is applied,
Relief of a specific call will be described. For each call, a caller object (hereinafter, CALL) is activated. This CALL
Generates an association when started. Objects involved in a series of call processing, such as a callee object and a call control object, sequentially participate in the association generated by the CALL, and the call connection is finally completed by unsubscribing.

If an object fails during call processing, that object sends a destruction message to the association. When recognizing this destruction message, the execution management layer 103 refers to the association management area ACB and determines whether or not the destination association of the destruction message is frozen. If the association is not frozen, the association is destroyed. When the association is destroyed in this way, the objects participating in the association are terminated or receive an initialization message from the association according to the initialization scheme specified at the time of the association. The object receiving the initialization message initializes itself according to an internal initialization procedure. As a result, the call processing involving the initialized object is interrupted and initialized.

On the other hand, if the association of the destination of the destruction message is frozen, the association is not initialized and call processing involving objects participating in the association is not interrupted. in this way,
An object that is involved in a specific call process can relieve the call by freezing the association in which the object participates.

By introducing the concept of association, which is a feature of the present invention, an application program can realize a system excellent in extensibility without depending on the form of a module. FIG. 5 shows an example in which the present invention is applied to a system composed of three physical modules.

FIG. 5 shows a system composed of three physical modules, Module A, Module B, and Module C. An application program existing on a certain module sends an association generation message to the execution management hierarchy of the module.
In response to this, a virtual association is generated, and each object sends a message of joining, leaving, or the like to this virtual association, regardless of which module the object exists on. That is, each object can access the virtual association without being bound by the physical structure of the module.

A physical association is generated for each module corresponding to the generated virtual association. The execution management hierarchy of each module actually manages the physical association of its own module. A set of physical associations of these modules is a virtual association. At this time, the physical association created in the module where the object that generated the association exists is called a master association. Also, a physical association generated by a module other than the module in which the master association is present and generated when a request to participate in the virtual association is made is called a slave association. FIG. 5 shows that an object existing on the module B generates a virtual association #, and a master association on the module B corresponding to the virtual association #.
An association Mx indicates that a slave association SAx has been generated on the module A. Fifth
The figure further shows that an object existing on module A creates a virtual association Y, and a master association My on module A, a slave association SBy on module B, and a module C on module C corresponding to this virtual association Y. This shows a case where the slave association SCy is generated.

The master association performs message communication with all the slave associations participating in the virtual association to which the master association belongs, and manages these slave associations. When an object sends a message for a virtual association,
First, the master association is activated. Thereafter, the master association sequentially activates the slave associations under its control. The slave association is activated from the master association and performs the required processing.

Here, the operation of each of the above-described components will be described by taking, as an example, a case where the system is restarted at the phase 1 level. In FIG. 5, it is assumed that the restart of the phase 1 has occurred in the module B, and for the sake of simplicity, it is assumed that each association is not frozen.

In module A, the execution management hierarchy determines whether the module that manages itself has a slave association that has a master association with the module that has resumed (that is, module B). In this case, module A has a slave association SAx having a master association with module B. The execution management hierarchy of module A destroys this slave association SAx. The execution management hierarchy of module A then determines whether the module it manages has a master association with a slave association with the module where the restart occurred (module B). In this case, module A has a master association having a slave association with module B.
There is My. The execution management hierarchy of module A destroys this master association My. When the master association My is destroyed, the master association My sequentially activates subordinate slave association destruction processing. Slave
The destruction of the association SCy is actually performed by the execution management hierarchy of the module C to which the slave association SCy belongs, similarly to the description of the destruction operation of the slave association SAx. Master Association My
Invokes its destruction process after all slave associations have been destroyed. In this way, even in a system including a plurality of modules, each object on the module can perform processing such as participation, withdrawal, destruction, and the like with respect to the virtual association.

As described above, by introducing the concept of association according to the present invention, initial setting can be performed by the same procedure in any system regardless of the physical structure of the system.

FIG. 6 summarizes the operations described above and shows an operation flow relating to the initial setting of an object when the system is restarted.

When the restart procedure is started, the execution management hierarchy of each module determines whether or not a restart has occurred in the module to which the module belongs (step 601). If resumption has occurred in the module to which the self belongs, it is determined whether the resumption level is phase 1 (step 602). Resumption level is Phase 1
If so, the physical association that has not been freed is deleted (step 607). Thereafter, it is determined whether or not each object under the module participates in the frozen association (step 608). If the object has participated in the frozen association, no processing is performed on the object, and the object is awaited to resume (step 610). On the other hand, for an object determined not to participate in the frozen association in step 608, the phase 1 initialization processing of the object is activated (step 609).

If it is determined in step 602 that the resumption is not the phase 1 level, then it is determined in step 603 whether the resumption is in the phase 2 level. Here, if it is determined that the resumption is in the third or fourth level, the system starts IPL (step 604). On the other hand, if it is determined in step 603 that the resumption of the phase 2 level is started, the phase 2 initial setting is started for each object under the module (step 60).
Five). Next, the physical association on the module is erased (procedure 606), and the process waits for completion of resumption (procedure 610).

If it is determined in step 601 that the module to which the self belongs is not a restart module, that is, if restart has occurred in another module, it is determined in step 611 whether the angular opening is at the phase 1 level. If the resume level is not Phase 1, for each physical association on the module,
It is determined whether it is a slave association (procedure 612). If it is a slave association, it determines if it has a master association on the resume module (step 613). If it has a master association, destroy its slave association (step 614). If there is no master association, no processing is performed for the association, and the end of the association is awaited for restart (step 617).

On the other hand, if it is determined in step 612 that the master association is a master association, it is determined whether or not it has a slave association on the resume module (step 61).
Five). If there is a slave association, destroy the association (step 616). Slave
If there is no association, the process directly waits for the restart end (step 617).

If it is determined in step 611 that phase 1 is to be resumed, it is determined whether the physical association is frozen (step 618). If it has been frozen, it is waited for restart (step 624). If the physical association has not been frozen, it is further determined whether it is a slave association (step 619).
If it is a master association, it further determines whether the master association has a slave association with the resume module (step 622).
If there is a slave association, the master
The association is destroyed (procedure 623), and the process waits for the end of resumption (procedure 624). If it is determined in step 619 that the association is a slave association, it is determined whether the association has a master association with the resume module (step 620). If the resume module has a master association, destroy the slave association (step 621). If there is no master association in the resume module, the process waits for the termination of the resume (step 624).

FIG. 7 shows the situation when the physical association is destroyed.
The initial setting operation of the object will be described.

When destroying a physical association, it is first determined whether or not the physical association is a master association (step 701). If it is a master association, the subordinate slave associations are sequentially destroyed (procedure 702), and thereafter the objects under the physical association are initialized (procedure 70).
3). On the other hand, if the physical association is a slave association in step 701, the
To initialize the subordinate objects. After the initialization of the subordinate object is completed, the object waits for the end of resumption (step 704).

FIG. 8 illustrates an initial setting operation to be performed on an object that has participated in a frozen association after the resumption processing is completed.

After the completion of the restart processing, the execution management hierarchy of each module determines whether the restart has occurred in the module to which the module belongs (procedure 801). If the restart has occurred in the module to which it belongs, it is determined whether the restart was a phase 1 level restart (procedure 802). In the case of a phase 1 level restart, for objects that have been participating in a physical association that has been frozen before that time, the restoration process according to the initialization method specified when the object joined the association is performed. Do (Step 80
Four). On the other hand, if it is determined in step 1 that the module is not a resumption module, that is, if resumption occurs in another module, it is determined whether the resumption was at the phase 1 level (step 803). If it is the resumption of the phase 1, the object participating in the physical association waiting for the resuming end is subjected to a repair process according to the initialization method specified at the time of the association participation (step 805).

(Effects of the Invention) As described above in detail, the present invention provides a software entity integrating processing procedures and data, that is, an electronic exchange constituted by an object, corresponding to each component of the electronic exchange. In the initial setting method, a plurality of objects that are functionally related to each other generate an association as a management unit for executing a program.

Therefore, functions such as restart processing and initial setting of a specific call which are closely related to the call processing can be freely described as objects without being affected by other parts of the program. Even if it is necessary to add or modify functions, program design and modification should be performed for each object.
It can easily respond to the addition, change, maintenance, and porting of service functions to other models. This is reliability,
This leads to the realization of replacement software with excellent maintainability, expandability, and verification.

In addition, by introducing the concept of association, each object is managed as one unit when executing software, and more efficient operation can be defined.

Furthermore, by introducing the concept of virtual association, each object can operate without being aware of the system configuration and module configuration, which is also advantageous for software design and porting to other models.

[Brief description of the drawings]

FIG. 1 is a diagram showing the positioning of an electronic exchange according to the present invention, FIG. 2 is a diagram showing the concept of an object, FIG. 3 is a diagram showing the relationship between an object and an association, FIG.
FIG. 5 is a diagram showing the structure of the execution management hierarchy, FIG. 5 is a diagram showing the relationship between the multi-module system and the virtual association, FIG. 6 is a diagram showing the operation related to the initial setting of the object when the system is restarted, FIG. 7 is a diagram showing the initial setting operation of the object when the association is destroyed, and FIG. 8 is a diagram showing the initial setting operation of the object at the end of the resumption processing. 100: Computer hardware, 101: Electronic exchange hardware, 102: OS, 103: Execution management hierarchy, 10
4… Application program, ACB …… Association management area, SCB …… Thread management area, OCB…
... Object management area.

──────────────────────────────────────────────────続 き Continued on the front page (72) Inventor Noriyuki Tomizawa 1-7-12 Toranomon, Minato-ku, Tokyo Oki Electric Industry Co., Ltd. (58) Field surveyed (Int. Cl. ⁶ , DB name) H04Q 3 / 54-3/545 G06F 9/44 530-535

Claims (3)

(57) [Claims] An object set that integrates a processing procedure and data corresponding to each component of the electronic converter;
In an initial setting method of call processing of an electronic converter in which a call connection is realized by the operation of the series of objects, the electronic converter manages an application program including a set of the objects, and manages execution of the application program. An execution management hierarchy that controls and further manages a plurality of said objects as an association, which is one initialization unit, wherein one of said objects generates an association in said execution management hierarchy, and said other one of said objects Performs the call connection operation by participating in the association, and when a system error occurs in the electronic converter, the execution management layer destroys the association, and with the destruction of the association, participates in the association. Object is initial Characterized in that it is constant, the initial setting method of call processing. 2. The method for initializing call processing according to claim 1, wherein said object can designate contents to be initialized when participating in an association. 3. The method for initializing call processing according to claim 1, wherein said object can designate an association created by itself or a participant in which the object participates as a non-destructive object.