JP3697467B2 - Switch object update system - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to an object update system for an exchange that updates an object in accordance with a change in system configuration that occurs during system operation or an increase or decrease in accommodation lines or subscribers in the object-oriented software of an electronic exchange.
[0002]
[Prior art]
As the system configuration is changed during operation of the switching system and the number of accommodation lines and subscribers is increased or decreased, the office data change work of the switching software occurs. Generally, in the online station data change, the command execution program performs a data change operation to be changed by a command input from a maintenance device connected to the exchange.
The station data changing operation in the object-oriented exchange software means performing an operation of changing the attribute of an existing object having station data or adding or deleting an object itself.
[0003]
[Problems to be solved by the invention]
In the station data changing process as described above, one station data changing operation includes a plurality of stages, and generally a plurality of objects (station data) are related. The operation of changing the data of each object or creating or deleting an object is executed sequentially and independently. The memory corresponding to the data area of the object is directly rewritten in these operation units.
Therefore, an error in changing station data due to an operator's operation error or the like is not detected until the operation is completed after the work is completed, which may impair the reliability of the system.
[0004]
Further, in the station data changing operation, if the system is restarted due to some trouble at each stage during the operation, station data contradiction occurs. In order to resolve this, it is necessary to restore the station data that was in the middle of the work at the time of resumption to the state before execution, but if the maintenance person knows how far the change operation has been performed, use the command You can switch back, but the procedure is very complicated. In addition, when it is not recognized how far the change has been made, it is necessary to load and resume the data backed up by the IPL procedure.
[0005]
From this point, it is possible to prevent the station data change error from being operated, and even if the work is stopped during the station data change work, the exchange does not require any special maintenance operation. The realization of the object update system was desired.
[0006]
[Means for Solving the Problems]
  The present invention employs the following configuration in order to solve the above-described problems.
<Structure of Claim 1>
  The present invention provides an object update system for an exchange comprising a large number of objects that execute exchange processing using current data for exchange processing, and for the update target object that requires updating of the current data, Register data as old data and update data as new data, create objects to be added along with the update, register added data as new data, delete deleted along with the update An object update control unit for registering data to be deleted with respect to the target object as old data, and when the registration notification is received from the object update control unit, the update target object, the additional object, and the deletion target object are inactive Construction mode data indicating An object management unit that assigns operation mode data indicating the current use to an object, and a test message is supplied to cause the update target and the additional object to execute an exchange process based on the new data, and when a predetermined exchange process is completed A message control unit that outputs a switching request, and the object update control unit, upon receiving the switching request, waits for the completion of execution of all objects and converts the construction mode data of the object management unit into operation mode data. An object update system for an exchange, wherein the new data is written into a data area corresponding to the update target object and the deletion target object and old data in the corresponding data area are deleted.
[0017]
DETAILED DESCRIPTION OF THE INVENTION
Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a block diagram showing an embodiment of an object update system for an exchange according to the present invention. Prior to this, a system as a basis of the system according to the present invention will be described.
[0018]
  FIG. 2 is a configuration diagram of the object-oriented exchange software.
  In the figure, the object-oriented exchange software includes a real-time OS 100, an object interfacer 101, and an application 102.
  The real-time OS 100 is an operating system that is located in a hierarchy on the computer hardware 200 and manages various processes performed by the computer.
  The object interfacer 101 has a function of providing an execution environment to the higher-level application 102 using the function of the real-time OS 100, and a message.managementA function, a thread management function, an object management function, a class management function, a memory management function, and the like.
[0019]
Here, the message management function is activated when an object performs message transmission, and has a function of determining a destination object, selecting an appropriate message transmission means, and delivering a message to the destination object. The thread management function is a function that provides a resource as a parallel processing unit for executing a transmission message. The object management function is a function for managing creation / addition / deletion of an object and a running state. The class management function is a function for managing attribute information such as an application program and a data size in a unit representing an object type called a class. The memory management function provides a function for capturing and releasing a memory area that is required when an object is added or deleted.
[0020]
The application 102 is software designed based on a concept called object orientation that encapsulates information and information processing operations and is accessed by messages, and is composed of various object groups to realize various services of the exchange system To do. Note that the exchange hardware 201 is hardware that performs exchange processing using exchange software including the real-time OS 100, the object interfacer 101, and the application 102.
[0021]
3 and 4 are explanatory diagrams showing an example of a model configuration diagram of the exchange system and an implementation of an application object corresponding thereto.
5 to 7 are data configuration diagrams of each object.
[0022]
  As shown in FIG. 3, the switching system includes a line accommodating device A110, a line accommodating device B111, a switching switch 112, a control device (CPU) 113, a maintenance terminal 114, and terminals A1 to A3, B1, and B2.
  The line accommodating device A110 is a device that accommodates the terminals A1 to A3 connected to the ports A1 to A3, respectively. The line accommodating device B111 is a device that accommodates the terminals B1 and B2 connected to the ports B1 and B2, respectively. is there. The exchange switch 112 has a function of switching communication from the line accommodation apparatuses A110 and B111. The control device 113 is a control device for controlling the line accommodating devices A110 and B111 and the exchange switch 112 via the control bus, and has an object configuration as shown in FIG. The maintenance terminal 114 is a terminal for inputting various instructions and displaying status. And the object in the control apparatus 113 shown in FIG.data fromIs as shown in FIGS.
[0023]
Next, as shown in FIG. 3, the operation of changing the station data will be described by taking as an example the case where the terminal A3 having the extension number “13” is moved from the accommodation position port A3 of the exchange to the accommodation position port B3.
[0024]
FIG. 8 is a flowchart of the station data changing operation, which is a comparison of the changing operation of the object update system of the exchange according to the present invention.
(1) In step S1, extension number “13” is deleted. In the object update operation, the variable data (table 1) of the number translation object shown in FIG. 7 is rewritten (data “empty” from the terminal “A3”) in the portion indexed by the number “13” (operation 1).
(2) In step S2, terminal A3 is deleted. In the object update operation, in operation 2, the data rewrite of the variable data (accommodation position conversion table) of the line accommodation apparatus A object of FIG. 5 indexed by the accommodation position number “2” (from “terminal A3” to “unimplemented”). )I do. In operation 3, the terminal A3 object is deleted (data area is released).
[0025]
(3) In step S3, terminal B3 is registered. In the object update operation, a new terminal class B3 object having the following variable data is generated (operation 4).
-Line accommodation object ID is "line accommodation apparatus B"
・ The accommodation position number is "2"
・ Extension number is “13”
[0026]
(4) In step S4, the port B3 is unblocked. In the object update operation, data rewriting (from “not mounted” to “terminal A3”) of the part where the variable data (accommodation position conversion table) of the circuit accommodation apparatus B object is indexed by the accommodation position number “2” is performed (operation 5). .
(5) In step S5, extension number "13" is added. In the object update operation, the data rewriting (from “empty” to “terminal A3”) of the portion indexed by the number “13” in the variable data (table 1) of the number translation object is performed (operation 6).
[0027]
As described above, as shown in FIG. 8, in the above station data changing operation, one station data changing operation includes a plurality of stages, and generally a plurality of objects (station data) are related. The operation of changing the data of each object or creating or deleting an object is executed sequentially and independently. The memory corresponding to the data area of the object is directly rewritten in these operation units. As a result, an error in changing station data due to an operator's operation error or the like is not detected until the operation is completed after the operation is completed.
[0028]
Further, in the station data changing operation shown in FIG. 8, if the system is restarted due to some failure at each stage during the operation, station data contradiction occurs. In order to solve this, it is necessary to restore the state before executing the station data change that was in the middle of the work at the time of restart. In this case, if the maintenance person knows how far the change operation has been performed, it can be switched back with a command, but the procedure becomes very complicated. In addition, when it is not recognized how far the change has been made, it is necessary to load and restart the data backed up by the IPL procedure.
[0029]
Furthermore, if a plurality of commands are executed at the same time and they access the same object (station data), the station data will be destroyed. Therefore, it is necessary to provide a restriction check function in the command execution control program with a restriction condition that only one command that can access the same type of data can be executed at the same time.
[0030]
9 and 10 are explanatory diagrams of conflicts between commands.
That is, FIGS. 9 and 10 are explanatory diagrams of the relationship between the command execution object relating to various station data changes and the change target object (station data).
For example, in the illustrated example, a plurality of commands can be executed simultaneously with respect to class B, and there is a risk of access conflict, so that commands 1 to 3 cannot be executed simultaneously.
Therefore, in order to prevent access conflicts in this way, even when a large amount of station data is changed, commands are executed sequentially, which becomes a factor that hinders work efficiency.
[0031]
Therefore, the object update system for an exchange according to the present invention manages a series of related station data change operations as one processing unit, thereby guaranteeing the update and recovery of station data in that unit, and is versatile for applications. The station data changing means is provided, and details thereof will be described below using a specific example.
[0032]
<< Specific Example 1 >>
<Constitution>
In FIG. 1, the object update system of the exchange includes a real-time OS 100, an object interfacer 101, and an application 102. Here, the real-time OS 100 is an operating system that manages various processes performed by the computer, as described with reference to FIG. The application 102 includes various object groups.
[0033]
The object interfacer 101 includes a message control unit 1, an object management unit 2, a class management unit 3, a memory management unit 4, a restart initial setting unit 5, a thread management unit 6, and an object update control unit 7.
[0034]
The message control unit 1 has the above-described message control function, and also has the function of exclusive control of the switching operation of the changed object from the construction environment to the normal operation environment and the access to the object during the switching operation. ing. The object management unit 2 has the above-described object management function, and also has a function of preparing a work environment different from the normal operation environment for changing work for objects registered in the work group. Further, the class management unit 3, the memory management unit 4, and the thread management unit 6 have the above-described class management function, memory management function, and thread management function. Further, the restart initial setting unit 5 has a function of performing initial setting when the exchange system is restarted. The object update control unit 7 has a function of managing an object group having data to be changed as one construction group when changing the object of the exchange.
[0035]
<Operation>
FIG. 11 is a flowchart of the station data changing operation of the first specific example.
FIG. 12 is an explanatory diagram of operations when changing station data.
FIG. 13 is an explanatory diagram of the management data configuration of the object management unit 2 and the object update control unit 7 when the station data is changed.
14 and 15 are explanatory diagrams of object states in each phase.
[0036]
FIG. 12 shows the relationship between the update target objects A, B, and C whose station data is being changed and the object update control unit 7 and the object management unit 2. Here, the object A is the change target object and the object B is added. Object and object C are examples of deleted objects.
[0037]
As shown in FIG. 13, the object management unit 2 includes an object management table 30. The object management table 30 includes an object state, a pointer to the operation mode to the object data area, a pointer to the construction mode, and The construction group number is indicated. The object update control unit 7 includes a construction group management table. The construction group management table shows a construction group status and a pointer to a group information list.
[0038]
The station data changing operation will be described below with reference to the flowchart of FIG.
(1) Phase 1 is a phase in which a command execution control object that has received a command from a maintenance person captures a “construction group number” from the object update control unit 7 prior to a station data change operation.
That is, in the above (1), as shown in FIG. 12, the command execution control object 20 captures the construction group number for the object update control unit 7. Here, the construction group 21 is assumed.
[0039]
(2) Phase 2 is a phase in which the objects A, B, and C that are subject to station data change are registered in the construction group 21 that has been previously captured, and this phase is repeated for the number of station data changes. Here, depending on the object changing method, the object update control unit 7 performs the following operations.
[0040]
(A) When “changing” an existing object (object A in FIG. 12), the object update control unit 7 creates a copy of the target object A and registers it in the construction group 21 in response to a “construction start request”. At this time, the underlying object is called “operation mode”, and the duplicate object is called “construction mode”. The state in which two objects are secured is notified to the object management unit 2 and stored in the “under construction” state on the object management table 30 shown in FIG.
(B) When adding a new object (object B in FIG. 12), the object update control unit 7 generates the object B and registers it in the construction group 21 in response to the “addition request”. The generated object B is treated as “construction mode” and notified to the object management unit 2.
(C) When deleting an existing object (object C in FIG. 12), the object update control unit 7 registers the object C in the construction group 21 in response to a “delete request”.
[0041]
As described above, the state transition of each object corresponds to the transition from phase 1 to phase 2 in FIG.
[0042]
(3) Phase 3 is a phase in which the application 102 actually changes the station data. This means that the variable data on the “construction mode” side generated by the object update control unit 7 is rewritten. This phase applies to “change” or “add” objects A and B. The access mechanism to the construction mode is described below.
[0043]
FIG. 16 is an explanatory diagram of a general concept of inter-object communication.
FIG. 17 is a processing flowchart of the message control unit 1 that realizes inter-object communication.
(A) As shown in FIG. 16, when the transmission source object 40 makes a message transmission request, the message control unit 1 determines whether or not to secure a resource (thread) necessary for message execution depending on the type of message transmission. When determining and performing {when asynchronous message: FIG. 16 (a)} is requested to the thread management unit 6, when not performing {when synchronous message: FIG. 16 (b)} is the current execution environment. The message is delivered to the destination object 41 using the thread 42 as it is. This is the process of step S1 in FIG. The thread 43 is a thread for starting up the destination object 41. As for the processing here, a known method is used, as described in, for example, Japanese Patent Application No. 2-28591 “Parallel Processing Method”.
[0044]
(B) Further, the message control unit 1 determines which mode the message is to be delivered to according to the thread execution mode and the state of the destination object 41 described below. This is the process of steps S2 to S9 in FIG.
(C) When the message is transmitted, the application 102 accesses the operation mode or the construction mode when the message destination object 41 is under construction for the threads 42 and 43 that are the message execution environment. Can be specified. This is an “execution mode setting request” for the thread, and as shown in step S3 in FIG. 17, any one of “operation mode access / construction mode access / test mode access” can be selected.
[0045]
FIG. 18 is an explanatory diagram of thread execution modes and message transmission.
The a) operation mode access setting, b) construction mode access setting, and c) test mode access setting in FIG. 18 are the thread execution mode operation mode access, construction mode access, and test mode access in step S3 of FIG. Corresponding.
[0046]
(D) When a message is transmitted on a thread designated as “construction mode access”, if the destination object 41 is under construction and has a construction mode, the message is executed on the construction mode side. That is, this state corresponds to b) construction mode access setting in FIG. When a message is transmitted on the thread designated as “operation mode access”, the message is executed on the operation mode side of the destination object 41 as shown in FIG. 18A (step S2 in FIG. 17). To the step S6).
(E) In phase 3, the program corresponding to the above message rewrites the variable data.
[0047]
(4) Phase 4 is a phase for confirming whether or not the station data has been correctly changed. This is realized by using the thread set for the test mode access shown in FIG. Hereinafter, the test operation will be described by taking the terminal accommodation change shown in FIGS.
FIG. 19 is a diagram for explaining the operation of the confirmation test.
That is, FIG. 19 shows a test configuration example for confirming the change of the station data in FIGS. 3 and 4. From the terminal 50 registered as the test terminal, the extension number “13” is dialed and the port A3 is dialed. It is assumed that the test confirms that the terminal 51 that has moved to the port B3 can receive a call.
[0048]
(A) When receiving a call signal from the test terminal 50, the corresponding test terminal object 52 starts a call processing operation.
(B) Upon receiving a dial signal from the test terminal 50, the test terminal object 52 sets the thread execution mode to “test access mode” and transmits a “number translation” request message 56 to the number translation object 53.
(C) The message transmission request is sent to the construction mode side when the number translation object 53 as the destination object is under construction by the message control unit 1.
(D) When the number translation is executed on the construction mode side of the number translation object 53, the object identification number of “terminal B3 object 58” is returned to the test terminal object 52 as a processing result.
[0049]
(E) The test terminal object 52 transmits an “incoming request” message 57 to the terminal B3 object 58.
(F) The message control unit 1 checks that the execution mode of the thread is “test access mode” and that the terminal B3 object 58 is under construction, and sends a message 57 to the construction mode of the terminal B3 object 58. deliver.
(G) Upon receiving the message 57, the terminal B3 object 58 delivers the message to the construction mode of the line accommodation apparatus B object 54.
(H) The message control unit 1 checks that the execution mode of the thread is “test access mode” and that the line accommodating apparatus B object 54 is under construction, and sets the line accommodating apparatus B object 54 to the construction mode. Deliver a message.
(I) When receiving the message 59, the line accommodating apparatus B object 54 transmits a calling signal to the line having the port number B3.
[0050]
(5) Phase 5 is a phase in which the station data to be operated is switched to new data that has been changed, and is executed in response to a “mode switching” request to the object update control unit 7. Hereinafter, the switching configuration will be described.
(A) When receiving the mode switching request, the object update control unit 7 transmits a “switch notice” message to all objects having the operation mode registered in the designated construction group.
(B) The object that has received the “switching notice” message executes the pre-switching processing program, and sweeps out any other processing that is being executed in the operation mode.
(C) Next, the object update control unit 7 inquires the object management unit 2 about the executing state of all the objects in the construction group and monitors whether there is no object being executed.
[0051]
(D) When it is detected that not all objects (operation mode) in the construction group are being executed, the object update control unit 7 executes a switching operation for each object. The state in which the above operations are performed corresponds to phase 5/6 in FIG.
(1) The “change” target object “exchanges” the operation mode and the construction mode, and sets the object state in operation. Note that “exchange” means a pointer reassignment operation to each mode in the object management data in FIG.
(2) The object object to be added is changed from the construction mode to the operation mode and the object state is in operation.
{Circle around (3)} The object to be “deleted” is changed from the operation mode to the construction mode and the object state is under construction. In this case, there is no operation mode, and general access to this object cannot be transferred.
(E) When the switching operation is completed, the object update control unit 7 transmits a “switching complete” message to all objects having the operation mode registered in the construction group.
(F) The object that has received the “switching complete” message executes the post-switching processing program.
[0052]
(G) If there is a message transmission request for an object that is being registered in the construction group during the switching operation, the corresponding request (thread) is sent to the object update control unit 7 in order to avoid processing inconsistency due to conflict with the switching operation. Registered in a waiting queue prepared in advance for each construction group.
[0053]
FIG. 20 is an explanatory diagram of waiting for object access during mode switching indicating this state.
The operation of the message control unit 1 in this case is as shown in the flowchart of FIG. That is, when there is a message transmission request from the object X, the message control unit 1 refers to the destination object state (step S2 in FIG. 17). If this is under construction, the construction group status is referred to (flow from step S3 to step S7 in FIG. 17). Here, since the construction group state is being switched, the thread waits for activation (step S8 in FIG. 17).
[0054]
(H) When all post-switching processes are completed, the object update control unit 7 extracts and executes the thread if it is registered in the waiting queue of the switched work group, and ends the switching routine.
(6) Phase 6 is a state in which the new station data is changed (provisional operation).
(7) Phase 7 is an end phase of the station data change work. When the object update control unit 7 receives the “construction end” message, it executes the release processing for the designated construction group (the following operations were performed) The state corresponds to phase 7 in FIG. 15).
(A) Release the construction mode of the object to be changed (the old data side before the change at this point).
(B) The “addition” target object does nothing.
(C) The “deletion” target object is deleted.
(D) Release the construction group number and its management data area.
[0055]
The process described above is an example of normal operation. When the application 102 wants to interrupt the process for some reason during the station data change work, by sending a “destroy request” message to the object update control unit 7, Station data can be restored.
[1] When suspending in phase 3 (under test), the objects registered in the designated construction group are operating in the old state, so that the original state can be restored by releasing the construction mode.
[2] When interrupting in phase 6 (provisional operation), the object registered in the designated construction group is operating in the new state, so the switching operation is executed again (the reverse operation of phase 5). After that, if the construction mode is released, the original state can be restored.
[0056]
<effect>
As described above, according to the specific example 1, the following effects can be obtained.
(1) The normal operation performed by the object to be changed during the station data change operation and the operation related to the station data change can be handled independently, and it can be confirmed whether or not the change operation has been performed reliably. Maintenance work can be performed reliably.
(2) Station data change while maintaining service continuity by guaranteeing that processing contradiction due to competition between station data switching operation and general processing does not occur in units of object groups having related data It can be performed.
(3) Since it is ensured that station data can be restored to its original state even if it is interrupted at an arbitrary stage using a series of related station data changing operations as a unit, the safety of maintenance work can be improved.
[0057]
<< Specific Example 2 >>
<Constitution>
FIG. 21 is a configuration diagram of the second specific example.
That is, the specific example 2 is an example of a distributed system composed of a plurality of control processors, and each processor performs various controls via a processor bus.
FIG. 22 is a configuration diagram of an object interfacer in each processor.
Each object interfacer is different from the first specific example shown in FIG. 1 in that an inter-processor communication control unit 8 is added. The inter-processor communication control unit 8 has a function of performing communication control between the processors. In FIG. 22, the internal configuration of the processors P2 and P3 is the same as that of the processor P1, and therefore the internal configuration is not shown.
[0058]
<Operation>
FIG. 23 is an explanatory diagram of an operation when the processor is restarted in the second specific example.
That is, the state shown in FIG. 23 shows the relationship between the application (object group) and the object update control unit 7 when the construction group shown in FIG. 12 is expanded to the distributed environment. The construction group conscious of is a distributed and transparent concept, and indicates that the object update control unit 7 existing in each control processor manages the construction group in cooperation with each other.
23, it is assumed that objects existing in the processor P1 and the processor P2 are registered in the construction group 1 and objects existing in the processor P2 and the processor P3 are registered in the construction group 2.
[0059]
(1) The restart initial setting unit 5 of the processor P1 starts initial setting routines of various control units by restarting the own processor.
(2) The initial setting routine of the object update control unit 7 of the processor P1 reads the construction group management table, and if there are construction groups that existed at the time of restart, all construction groups are registered in that group. After restoring the object in the local processor, the construction group is released. In the example of FIG. 23, object A and construction group 1 correspond to this.
(3) When receiving the initial setting request, the inter-processor communication control unit 8 of the processor P1 transmits a restart notification message to all other processors. When the inter-processor communication control unit 8 of the other processor that has received the notification notifies the restart initial setting unit 5, the restart initial setting unit 5 starts up another processor restart routine of the various control units.
[0060]
(4) The other processor restart routine of the object update control unit 7 reads the work group management table, and if there is a work group that exists at the time of the restart, all the work groups are registered in the group. After restoring the objects in the processor, release the construction group. In the example of FIG. 23, the processor P2 restores the objects B and C and releases the construction group 1 and the construction group 2. In the processor P3, the object D is recovered and the construction group 2 is released.
[0061]
<effect>
As described above, according to the second specific example, in a multiprocessor system, when some of the processors are restarted during the station data changing operation, all the station data changing operations in the middle of the processing are restored. It is no longer necessary to restart the entire system to solve the problem. This leads to an improvement in system reliability.
[0062]
In the specific example 2, when any of the processors resumes, all the objects are restored to the state before registration, but only the objects related to the resumed processor are restored to the state before registration. You may comprise as follows. For example, in the example shown in FIG. 23, the object update control unit 7 of the processors P1 and P2 releases the construction group 1 and restores the objects belonging to the construction group, but the object update control unit 7 of the processors P2 and P3 The state of construction group 2 is left as it is.
[0063]
By configuring in this way, the change operation of the construction group 2 can be resumed in a continuous state, so that the processing results up to that point can be utilized, and therefore the station data change process can be promptly terminated. it can.
[0064]
<< Specific Example 3 >>
Specific Example 3 describes a conflict detection mechanism between commands when a plurality of commands are input at the same time.
The registration operation of the target object in the construction group in phase 2 of FIG. 11 is as shown in the specific example 1 above. However, the object update control unit 7 performs the registration, “whether the designated object is already under construction. Check “”. This is performed by referring to the object state in the object management table 30 shown in FIG. If so, the registration request is rejected. This means that "the object can register only one construction group at the same time".
[0065]
In the phase 3 in FIG. 11, the station data rewriting of the object is realized by setting the execution mode of the thread to “construction access mode” in advance and transmitting a message on the thread. The thread management unit 6 further has the following functions.
[0066]
(1) When the execution mode of a thread is set to “construction access mode”, the construction group in which the destination object is registered and the thread are related and stored by the thread management unit 6.
(2) When the message control unit 1 activates the destination object in the “construction mode access” thread, the message control unit 1 compares the construction group related to the thread with the construction group in which the destination object is registered. If it does not match, the message transmission request is rejected.
This operation corresponds to b) of FIG. That is, the object C shown in FIG. 18 is registered in the construction group 1, and the object D registered in the construction group 2 cannot be accessed. This means that “station data cannot be rewritten across a plurality of construction groups”. This operation is performed when the thread execution mode in step S3 in FIG. 17 is the construction access mode. In this case, in step S9, it is checked whether or not the registered construction group and the construction group related to the thread match. If they match, the process proceeds to step S5 to extract the construction mode pointer. An error is returned due to the prohibition of access across different construction groups.
[0067]
<effect>
As described above, in the specific example 3, only one construction group can be registered at the same time, and rewriting of station data cannot be performed across a plurality of construction groups. The conflict detection by execution can be left to the object interfacer 101, and it is not necessary to prepare a unique conflict check logic according to the type of command. As a result, it is not necessary to execute commands sequentially, and an environment in which a plurality of commands whose objects to be changed are completely irrelevant can be executed at the same time is constructed, and the efficiency of maintenance work can be improved.
[0068]
【The invention's effect】
As described above, according to the object update system of the exchange of claim 1, the normal operation performed by the object to be changed during the change of the station data and the operation related to the change of the station data can be handled independently. Further, since it is sufficient to confirm whether or not the change operation has been performed reliably for the object in the construction mode, the maintenance work can be reliably performed. In addition, even if a series of related station data change operations are interrupted at any stage, it is possible to guarantee that the station data is restored to the original state, so that the safety of maintenance work can be improved. Furthermore, it is assured for each group of objects having related data that there is no processing inconsistency due to a conflict between station data switching operation and general processing, and station data is maintained while maintaining service continuity. Changes can be made.
[0069]
According to the object update system for an exchange according to claim 2, it is possible to eliminate data inconsistency between processors without managing how much change operation has been performed in which construction group when any control processor is restarted. There is no need to restart the entire system to make it happen.
[0070]
According to the object update system for an exchange according to the third aspect, since the change operation in the construction group unrelated to the resumed control processor can be continued as it is, the station data change process can be promptly terminated.
[0071]
According to the object update system for an exchange according to claim 4, an environment in which a plurality of commands that are access between objects that do not belong to a construction group, that is, objects that are completely irrelevant objects can be executed at the same time is constructed. Can be achieved.
[Brief description of the drawings]
FIG. 1 is a configuration diagram showing an embodiment of an object update system for an exchange according to the present invention.
FIG. 2 is a configuration diagram of object-oriented exchange software.
FIG. 3 is a model configuration diagram of an exchange system.
FIG. 4 is an explanatory diagram showing an example of implementation of an application object corresponding to a model of an exchange system.
FIG. 5 is a data configuration diagram (No. 1) of each object;
FIG. 6 is a data configuration diagram (part 2) of each object;
FIG. 7 is a data configuration diagram (No. 3) of each object;
FIG. 8 is a flowchart of a station data change operation that is a comparison of the change operations of the present invention.
FIG. 9 is an explanatory diagram (part 1) of conflicts between commands.
FIG. 10 is an explanatory diagram (part 2) of conflicts between commands.
FIG. 11 is a flowchart of a station data changing operation in the first specific example.
FIG. 12 is an operation explanatory diagram when changing station data;
FIG. 13 is an explanatory diagram of management data configurations of an object management unit and an object update control unit when station data is changed.
FIG. 14
It is explanatory drawing (the 1) of the object state in each phase.
FIG. 15 is an explanatory diagram (part 2) of an object state in each phase.
FIG. 16 is an explanatory diagram of a general concept of inter-object communication.
FIG. 17 is a processing flowchart of a message control unit that realizes inter-object communication;
FIG. 18 is an explanatory diagram of thread execution modes and message transmission;
FIG. 19 is an explanatory diagram of an operation of a confirmation test.
FIG. 20 is an explanatory diagram of waiting for object access during mode switching.
FIG. 21 is a configuration diagram of specific example 2;
FIG. 22 is a configuration diagram of an object interfacer in each processor of specific example 2;
FIG. 23 is an explanatory diagram of an operation when the processor is restarted in specific example 2;
[Explanation of symbols]
1 Message control unit
2 Object Management Department
7 Object update controller
101 Object interfacer
102 Application (object group)

Claims (1)

In an object update system of an exchange comprising a large number of objects that perform exchange processing using current data for exchange processing,
The current data is registered as old data and the update data is registered as new data for the update target object that needs to be updated, and an object to be added is generated along with the update. An object update control unit for registering data to be deleted as old data, and registering data to be deleted with respect to an object to be deleted that is deleted as a result of the update,
When the registration notification is received from the object update control unit, construction mode data indicating non-working is given to the update target object, the additional object, and the deletion target object, and operation mode data showing the current use to other objects An object management unit that grants
A message control unit that supplies a test message to cause the update target and the additional object to execute an exchange process based on the new data, and outputs a switching request when a predetermined exchange process is completed,
Upon receiving the switching request, the object update control unit waits for the completion of execution of all objects, converts the construction mode data of the object management unit to operation mode data, and sets the data area corresponding to the update target object. Writing the new data and deleting the old data of the object to be deleted and its corresponding data area;
An object update system for an exchange.

Images