JP2003345615A - Operation system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To avoid the occurrence of a deadlock in control over a transmission device by an operation system. <P>SOLUTION: A request acceptance part 3 accepts one of control requests from a plurality of request clients 1. An MO class 4 registers the state of a network constitution element (a transmission device 8, a device constituting the transmission device 8, etc.), as the object of the accepted control request in an instance state table as a lock state showing removal of control by another control request or a queuing state showing a control wait state by another control request. After the registration, the request acceptance part 3 receives a next control request from the request client 1. Further, the network constitution element registered in the lock state is controlled after the registration and the state of the network constitution element whose control is completed is erased from the instance state table. <P>COPYRIGHT: (C)2004,JPO

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to an operation system for controlling a transmission device constituting a communication network system, a network element including the device constituting the transmission device, and an exclusive control method for the operation system. The present invention relates to an operation system and an exclusive control method that can avoid occurrence of a deadlock.

[0002]

2. Description of the Related Art In an operation system for monitoring and controlling a plurality of transmission devices constituting a communication network system, components such as transmission devices and hardware and software constituting the transmission devices are modeled and handled by an object-oriented model. Have been. FIG.
1 is a physical implementation diagram of a transmission device of a communication network system and a logical model diagram in which the transmission device is modeled by an object-oriented model.

[0003] The transmission device # 1 is one of a plurality of transmission devices constituting a communication network system. This transmission device # 1 has a bay (Ba) as shown in the physical mounting diagram of FIG.
y) It has packages (PKG) # 1 to # 3 of # 1, unit (Unit) # 1 and # 2, and unit # 1, and packages # 1 to # 3 of unit # 2.

[0004] A "bay" is hardware representing the entire transmission device, and a "unit" corresponds to, for example, a board housed in the bay. The “package” corresponds to a circuit element (such as an IC chip) attached to the unit or a circuit module including a plurality of circuit elements. Other transmission devices have the same configuration, and have bays, units, and packages.

[0005] In the object-oriented model, individual bays, individual units, and individual packages of the communication network system are associated with instances (objects). Also, a set having multiple bays as instances is represented as a class “Bay”,
A set having a plurality of transmission device units as instances is represented as a class “Unit”, and a set having a plurality of transmission device packages as instances is represented as a class “package (PKG)”.

[0006] Since these classes are object classes managed by the operation system, they are managed object (Managed Object) classes (hereinafter referred to as “MO”).
Class. ).

[0007] Each instance is provided with identification information (instance ID) for uniquely identifying the instance.
The instance is specified by D. For example, bay # 1
The instance ID of the unit # 1 in the bay # 1 is 0101, and the instance ID of the unit # 1 in the bay # 1 is 0101.
The instance ID of the package # 1 is 010101.

FIG. 13 is a functional block diagram showing the configuration of a conventional operation system 100. The operation system 100 includes a plurality of (here, two) requesting clients 101 and 102 and a plurality of (here, two)
MO class 103 and 104, device control unit 10
5, and multiple (here, two) databases (D
B) having 106 and 107;

The requesting clients 101 and 102
For example, corresponding to a terminal device operated by a user (operator) or an input / output window (screen) displayed on the terminal device, a request from the operator is input, and a processing result of the input request is displayed on the display device. Display on the screen.

The MO class 103 is a unit MO class, and the MO class 104 is a package MO class. The illustration of the bay MO class is omitted. The MO class 103 is an object generation unit 103
a, exclusive object detection unit 103b, exclusive control unit 10
3c, a timer monitoring unit 103d, and a database management unit 103e. The MO class 104 has the same configuration as the MO class 103, and the object generation unit 104
a, exclusive object detection unit 104b, exclusive control unit 10
4c, a timer monitoring unit 104d, and a database management unit 104e.

The databases 106 and 107 are MO
The management data of the class is managed as nonvolatile data.
Device control unit 105 is via the communications network 20 of the communications network system connected to a plurality of transmission devices 8 ₁ to 8 _m, the operating system 100 and transmitter 8 ₁
Data transmission / reception is performed in accordance with a communication protocol of up to 8 _m .

Such an operation system 100
Then, it is important to ensure the normality or consistency of the management data of the network components. Therefore,
In order to guarantee the normality or consistency of the management data and simultaneously execute control requests from a plurality of users, a lock function for restricting access to a database holding the management data of network components is used. The operation of the operator system 100 using the lock function will be described below.

[0013] When the user sends the MO
Instance ID of class 103 = 0101 (bay # 1
When a certain control A is requested for an instance of the unit # 1) (hereinafter referred to as “instance 0101”; the same applies to other instances), first, the object generation unit 103a generates an instance 0101 (object). Then, the instance 0101 is registered in a locked state in the instance state table of the database management unit 103e shown in FIG. By registering in the locked state, control of the instance 0101 from another user is restricted. This avoids a situation in which the normality or consistency of data is not maintained due to simultaneous control from a plurality of users.

Thereafter, the exclusive object detection unit 103b
Detects whether there is any other object (instance) to be exclusively controlled. For example, MO class 104
When the control B for the instance 010102 is required, the object generation unit 104a
An object 10102 is generated, and the instance 010102 is registered in a locked state in the instance state table of the database management unit 104e shown in FIG.

Thereafter, the exclusive object detecting unit 104b
Is the object (instance) to be exclusively controlled
Detects if exists. Here, it does not exist. Thus, a series of object generation and lock are completed.

When the object generation is completed, the requesting client 101 sends an exclusive control request to the exclusive control unit 103c, and the exclusive control unit 103c performs exclusive control on the instance 0101 of the MO class 103 and the MO class 104.
Of the exclusive control unit 104c. By performing the exclusive control, the control data and the like become MO class 1
From 03 to the transmission device via the device control unit 105, the transmission device is controlled.

The exclusive control unit 104c is provided with an exclusive control unit 103.
The instance 01010 of the MO class 104 as in the case of c.
2 is subjected to exclusive control. When a series of exclusive control processing is completed, the exclusive control unit 103c
To the exclusive control result.

The requesting client 101 displays the control result. Then, the object generation unit 103a outputs the MO
The object of the class 103 is deleted (erased). At this time, the object of the MO class 104 is also deleted at the same time. Thus, a series of processing is completed.

[0019]

However, in the simultaneous execution control using the lock function, a phenomenon called deadlock may occur depending on the request timing from a plurality of requesting clients. FIG. 15 is an operation sequence diagram showing the occurrence of deadlock in the conventional operation system 100.

The requesting clients 101 and 102
Assume that both instances need to be locked to control the instance 0102 of the MO class 103 and the instance 010202 of the MO class 104.

Here, the requesting client 101 sends the MO
The case where the request client 102 attempts to lock the instance 010202 of the MO class 104 and then locks the instance 0102 of the MO class 103 after locking the instance 010202 of the class 103 is locked. Think. At this time, MO class 103
And 104 start locking at almost the same time, the MO class 103 can register the instance 0102 in a locked state, but the instance 010202 has already
Because it is registered in the locked state by class 104,
The instance 010202 is registered in a queuing state (waiting state). On the other hand, MO class 104
Can register the instance 010202 in the locked state, but cannot register the instance 0102 in the locked state and register it in the queuing state.

In such a state, both MO classes keep waiting for the lock of the instance registered in the queuing state to be completed, and the processing is not completed forever. This state is called deadlock.

Object generators 103a and 104
In the queuing state, a issues a monitoring request to the timer monitoring units 103d and 104d, respectively, and outputs a lock completion event from the database management units 103e and 104e or the timer monitoring units 103d and 10d.
It will wait for a timeout event from 4d, respectively. The object generation units 103a and 104a
Normally, a series of object creation is completed by receiving a lock completion event, but if a deadlock is occurring, a timeout event is received. Then, the requesting clients 101 and 102 display a timeout error response.

As described above, in the conventional operation system, when requests from a plurality of requesting clients conflict with each other, a deadlock may occur and a timeout error may occur.

Although exclusive control is executed only after a series of object generation is completed, the queuing time cannot be predicted, so that the user cannot predict the total execution time including the queuing time.

An object of the present invention is to avoid the occurrence of deadlock in the control of a transmission device and a device constituting the transmission device by an operation system.

[0027]

An operation system according to the present invention is an operation system for controlling a transmission device constituting a communication network system and a network component including a device constituting the transmission device, wherein the network component is provided. A control request input unit for inputting a control request to the control request input unit, a request receiving unit for receiving the control request input to the control request input unit, and a first network element serving as a target of the control request received by the request receiving unit. A lock state indicating the exclusion of control by another control request between the state and the state of the second network element that requires elimination of control by another control request due to the control of the first network element. Or, a storage unit for storing as a queuing state indicating the end of control by another control request If the state of the same network element is already stored in the storage unit for each of the first and second network elements, the state is stored in the storage unit as a queuing state; A storage management unit that, when not stored, stores the locked state in the storage unit, and deletes the state from the storage unit upon completion of control; and a request reception unit, wherein the request reception unit is After the storage management unit finishes storing the state of the received control request, the next control request is received from the control request input unit.

An exclusive control method according to the present invention is an exclusive control method for an operation system for controlling a transmission device constituting a communication network system and a network element including the device constituting the transmission device, wherein the exclusive control method is provided by a user. A control request for the network element is received, and it is necessary to exclude a control by another control request accompanying the control of the first network element and the first network element to which the received control request is applied. If the state of the same network element is already stored in the storage unit for storing the state of the network element for each of the two network elements, the state is changed to the end of control by another control request. Storing in the storage unit a queuing state indicating waiting, If not, it is stored in the storage unit as a lock state indicating the exclusion of control by another control request, and after the storage processing of the received control request in the storage unit is completed, the user receives a request from the user. When the next control request is received and the control of the first and second network components is completed, the state is deleted from the storage unit.

According to the present invention, one control request input from the control request input unit is received by the request receiving unit, and the state of the first network element to be controlled and the first network configuration With the control of the element,
After the state of the second network element, for which control by another control request needs to be excluded, is stored in the storage unit,
The next control request is received by the request receiving unit.
Therefore, as described in the related art section, it is possible to avoid a deadlock state in which two control requests are accepted and each of them waits for the other party to complete the control.

The network components stored in the storage unit in the locked state are processed (controlled) according to the control contents indicated by the control request. After the control ends, the state of the network element is deleted from the storage unit.

[0031]

DESCRIPTION OF THE PREFERRED EMBODIMENTS An operation system according to an embodiment of the present invention will be described below.

<Configuration of Operation System> FIG.
Is an operation system according to an embodiment of the present invention.
FIG. 2 is a functional block diagram showing the entire configuration of the system 10. This o
The operation system 10 includes n (n is an integer of 2 or more).
Number) request client 1₁~ 1_n, Queuing factor table
Client 2, request receiving unit 3, three MO classes 4
₁~ 4_Three, Three databases (DB) 5 ₁~ 5_Three, And equipment
A position control unit 6.

The apparatus control unit 6 of the operation system 10 is connected to a communication network 20, via the communication network 20, the transmission device 8 _1-8 of m constituting the communication network system (m is an integer of 2 or more) Communicates with _m . This communication, control and management of the transmission device 8 ₁ to 8 _m is performed.

The requesting clients 1 ₁ to 1 _n are, for example, C
A display device such as an RT display or a liquid crystal display, or a window (screen) displayed on one display device
And mainly executes processing of an input / output interface with a user (operator). Request Client 1
_{Since 1} to 1 _n all have the same configuration,
Unless it is particularly necessary to distinguish them, they are collectively referred to as requesting clients 1.

FIG. 2 is a functional block diagram showing a detailed configuration of the request client 1. The requesting client 1
It has a request information input unit 11, a result display unit 12, a cancel control unit 13, and an execution control unit 14.

The request information input unit 11 provides (displays) an input interface for inputting request information from the user to the user. The input interface includes a column for designating a communication network system component (transmission device (bay), unit, or package) (hereinafter also referred to as a “network component”), control contents for the network component (eg, register values). Read,
Changing register values, erasing (removing) units, etc.)
And the like are provided. The user monitors and controls the network components by inputting necessary data in these fields. The input data is provided from the request information input unit 11 to the execution control unit 14 as request information.

The result display unit 12 displays, on a display device (screen, window), response information to the request information given from the request receiving unit 3 via the execution control unit 14.

The cancel control unit 13 inputs and controls an instruction to cancel the request information input to the request information input unit 11 to perform monitoring and control. The cancel control unit 13 has an input unit different from the request information input unit 11 on the display device or window of the request client 1, and the user inputs a message ID required for cancellation via the input unit. Can be.

The execution control unit 14 provides the request information provided from the request information input unit 11 to the request receiving unit 3 as a request message, and also receives the cancel information input to the cancel control unit 13 as a cancel message. Give to. Further, the execution control unit 14 provides the response information provided from the request receiving unit 3 to the result display unit 12.

FIG. 3 shows the structure of a request message given from the requesting client 1 to the request receiving unit 3.
The request message includes a request client ID, a message ID, an MO class ID, an instance ID, a control ID,
And control argument data items.

The "request client ID" is identification information for uniquely identifying the request client. The execution control unit 14 holds the request client ID of the request client 1 to which the execution control unit 14 belongs, and stores the held request client I
Write D to the request message. Therefore, the request client ID included in the request message indicates the request client ID of the transmission source (request source) of the request message.

"Message ID" is identification information for uniquely identifying a request message. Message ID
Is unique in each requesting client 1.

"MO class ID" is identification information for uniquely identifying an MO class. The execution control unit 14 stores in advance table data in which the MO class to which the network component belongs and the MO class ID are associated with each other. The execution control unit 14 uses this table data to execute the network component M included in the request information.
The O class ID is obtained, and the obtained MO class ID is written in the request message. Therefore, the MO class ID included in the request message is the MO class ID of the transmission destination of the request message.
Indicates the class ID.

"Instance ID" is identification information for uniquely identifying an instance. Execution control unit 14
Stores in advance table data in which network elements are associated with instance IDs.
The execution control unit 14 uses the table data to execute the instance ID of the network component included in the request information.
And writes the obtained instance ID in the request message. Therefore, the instance ID included in the request message indicates the instance ID to be controlled by the request message.

The "control ID" is identification information for uniquely identifying control for a network element. The execution control unit 14 stores in advance table data in which control contents and control IDs are associated with each other. The execution control unit 14 obtains a control ID corresponding to the control content input by the user from the table data, and writes the obtained control ID into a request message. Therefore, the control ID included in the request message indicates the control ID of the instance to be controlled.

The "control argument" is an argument necessary for control corresponding to the control ID. For example, when the value of a register of a certain package is changed, the changed value (the value input by the user) is used. Written in the control message as control arguments.

The cancel message has a requesting client ID and a message ID to be canceled. As the message ID, when the execution control unit 14 transmits the request message, the message ID written in the request message is the request information input unit 11 or the cancel control unit 13.
To be displayed on a display device. This allows the user to know the message ID,
Canceling message ID at the time of cancellation
3 can be entered.

The queuing factor display client 2 shown in FIG. 1 has a queuing factor display unit 21 and a queuing factor search unit 22 as shown in FIG. When an object is registered in the MO class in the queuing state, the queuing factor search unit 22 searches the registration list that is the cause of the queuing state.
The queuing factor display unit 21 displays a registration list that is a factor of the queuing state.

The request receiving section 3 shown in FIG. 1 sequentially receives request messages from the request client 1 one by one,
Related to MO class sends the object message to the display client 1 to the associated response sent from the MO class 4 _{1-4 3.} The request receiving unit 3 receives the queuing factor search request from the queuing factor display client 2 and transmits it to the relevant MO class, and also transmits the queuing factor search result from the MO class to the queuing factor display client. 2
Give to.

FIG. 5 is a functional block diagram showing a detailed configuration of the request receiving section 3. As shown in FIG. The request receiving unit 3 includes a request receiving control unit 31 and a request state managing unit 32.

The request reception control unit 31 sequentially receives request messages transmitted from the request client 1 one by one. For example, when there are a plurality of requesting clients having a request message to be transmitted, the request reception control unit 31 receives the request message from the requesting client to which the transmission right has been given by giving the transmission right to only one of the requesting clients. I do. Then, the request reception control unit 31 becomes ready to receive the next request message when the object generation and the registration to the instance status table (described later) are completed for the received request message, and the next request message is received. Receive. By sequentially receiving and processing the request messages one by one in this manner, the occurrence of deadlock is prevented.

[0052] request acceptance control unit 31, along with providing the received request message to the requesting state management unit 32, among the MO class ₄₁ to _3, object generation message corresponds to MO class ID included in the request message Send This object creation message has the same configuration as the request message (see FIG. 3).

The request status management unit 32 holds and manages a request status table 32a. The request status management unit 32
Generates a request status list (a list in a horizontal row in FIG. 5) based on the request message given from the request reception control unit 31, and stores the generated request status list in the request status table 3.
In addition to 2a, the request status list that has become unnecessary is deleted (erased) from the request status table 32a.

Each request status list in the request status table 32a includes a reception time, a request client ID, and a message I.
D, MO class ID, instance ID, control ID, state, actual processing time, and start time.

The "reception time" is the time at which the request reception control unit 31 receives a request message from the request client 1 and registers it in the request state table. As the reception time, the time of a clock (not shown) held by the operation system 10 is used.

The "requested client ID", "message ID", "MO class ID", "instance ID",
The “control ID” used in the request message is used as it is.

"Status" indicates the status of the request message, and its status value is "executing" or "queuing". “Queuing” means a state in which an instance of the request state list is already controlled by another request state list (request message) and cannot be controlled immediately. “Executing” means that the control indicated by the control ID is being performed on the instance of the request state list.

The "substantial processing time" indicates the time required for control. The request state management unit 32 (or the request reception control unit 31) previously holds the substantial processing time corresponding to the control ID, and when registering the request state list in the request state table, adds the actual processing time to the control ID of the request state list to be registered. Write the corresponding real processing time to the request state list.

The "start time" indicates the time at which the status of the request control list is set to "running" and control of an instance of the request control list is started. This start time also
Similarly to the reception time, the time of a clock (not shown) held by the operation system 10 is used.

[0060] Returning to FIG. 1, DB 5 ₁ to 5 ₃ holds data for the corresponding MO classes ₄₁ to ₃ instances. This data includes the attributes of the instance (for example, the transmission speed of the network element, the clock frequency, etc.).

The MO classes 4 ₁ to 4 ₃ correspond to the classes of the respective objects obtained by modeling the network components by the object-oriented model, and manage and control the instances in which the network components are modeled. For example, MO class 4 ₁ corresponds to the object class of the transmitting apparatus _{(Bay) 8 1 ~8 m,} MO class 4 ₂ corresponds to the object class of the unit (Unit) of the transmission device, M
O Class 4 ₃ corresponds to the object class of the unit package (PKG). MO Class 4 _{1-4 3,} since both have the same configuration, hereinafter, unless otherwise it is necessary to distinguish, are collectively referred to as MO class 4.

FIG. 6 is a block diagram showing a detailed configuration of the MO class 4. The MO class 4 includes an object generation unit 41, an exclusive object detection unit 42, an exclusive control unit 4
3 and a database management unit 44.

The object generating unit 41
, Generates an instance (object) of the instance ID included in the received request message, and sends a request to register the generated instance to the database management unit 44. This registration request includes the instance I included in the object creation message.
When the exclusive object detecting unit 42 including the D, the requesting client ID, and the message ID locks an object belonging to its own MO class, the other MO to be locked in relation to this object is locked.
Search for objects belonging to a class.

The exclusive control unit 43 is provided with the database management unit 4
4 and performs exclusive control on the instance of the MO class to which it belongs.

The database management unit 44 holds the instance state table 44a, and stores the
Based on the registration request from, an instance state list (a row of data in the instance state table), which is an element of the instance state table, is generated, and the generated instance state list is added to the instance state table. The instance state list has an instance ID, a request client ID, a message ID, a state, and a reception time.

<Operation Sequence of Operation System> FIG. 7 is an operation sequence diagram of the operation system 10.

The request information from the user is input from the request information input unit 11 of the request client 1 and then given to the execution control unit 14. The execution control unit 14 transmits the request information to the request receiving unit 3 as a request message (see FIG. 3).

The request reception control unit 31 of the request reception unit 3 receives one request message and registers the received request message in the request state table (S1). At the time of registration, the time at the time of registration is written in the reception time of the request state table, and "queuing" is written in the state as a temporary state value. Further, the real processing time corresponding to the control ID is written in the real processing time. No time is written in the start time. For example, a value that does not represent the time (for example, N
UL etc.).

Next, the request reception control unit 31 sets the MO class 4 having the MO class ID included in the request message.
An object creation message having the same contents as the request message is transmitted to the following (MO class #A).

The transmitted object generation message is an object generation unit 41 of MO class #A (hereinafter referred to as “object generation unit 41 # A”; MO class #).
The other components of A are also denoted by “#A” after the reference numerals. ) Is received.

Upon receiving the object generation message, the object generation unit 41 # A generates an instance (object) of the instance ID included in the object generation message (S2), and generates the instance ID of the generated object, the request client ID, And a registration request including the message ID to the database management unit 44 # A.

The database management unit 44 generates an instance status list based on the registration request and adds it to the instance status table (S3). At the reception time of the generated instance state list, the object generation unit 41
Is received when the object creation message is received or when the instance state list is created.

The database management unit 44 # A searches the instance state table 44a # A and finds the same instance ID as the instance ID included in the registration request.
It is checked whether the instance state list having is already registered in the instance state table. The database management unit 44 # A has the same instance ID
If the instance status list having the ID has already been registered, the status value of the newly registered instance status list is set to "queuing" and the same instance ID is set.
If is not registered, the status value is “locked”.
Here, it is assumed that the same instance ID is not registered and the status value is “locked”.

Further, the object generation unit 41 # A
The MO class ID, the instance ID, and the control ID included in the request message are transmitted to the exclusive object detection unit 42.
Give to #A.

The exclusive object detection unit 42 # A receives the MO class I given from the object generation unit 41 # A.
Based on D, the instance ID, and the control ID, another object to be excluded, that is, an object to be locked and not to receive a control request from another requesting client (hereinafter referred to as an “exclusive object”). And the control ID and control argument for the exclusive object.

This is because the exclusive object detection unit 42 # A
Is obtained by the exclusive object detection table included in or the calculation performed by the exclusive object detection unit 42 # A. For example, when performing control to delete a unit (remove a unit from the bay), all packages included in the unit are detected as exclusive objects by the exclusive object detection table or calculation, and A control ID and a control argument for the exclusive object are obtained.

Here, one of the other MO classes 4 (hereinafter referred to as “MO class #B”) different from MO class #A.
It is assumed that one instance is detected as an exclusive object. In this case, the exclusive object detection unit 42
#A is the MO class ID of the MO class #B, and the instance I of the detected exclusive object (instance)
D, the control ID of the exclusive object, and the control argument of the exclusive object are returned to the object generation unit 41 # A.

When receiving the information of the exclusive object from the exclusive object detection unit 42 # A, the object generation unit 41 # A
An object creation message to be transmitted to class #B is created, and the created object creation message is sent to MO class #B. If no exclusive object is detected, the object generation unit 41 # A
A response message described later is returned to the request receiving unit 3 without creating an object generation message.

This object creation message includes the request client ID and the message ID in addition to the instance ID, control ID, and control argument of the exclusive object. The request client ID and the message ID are the same as those included in the request message received by the object generation unit 41 # A from the request reception unit 3.

MO Class #B Object Generation Unit 41
#B generates an object (instance) in the same manner as the MO class #A (S4), registers an instance state list in the instance state table 44a # B (S5), and registers the other in the exclusive object detection unit 42 # B. To detect an exclusive object to be excluded. When the exclusive object detecting unit 42 # B detects the exclusive object, the same processing as when the exclusive object detecting unit 42 # A detects the exclusive object is repeated.

Here, it is assumed that the instance state list is registered as a locked state in the instance state table 44a # B.
It is assumed that #B has not detected an exclusive object.

If the exclusive object is not detected, the object generation unit 41 # B does not transmit the object generation message, and sends a response message (ACK) notifying the end of the object generation to the object generation unit 4 # B.
Return to 1 # A. Upon receiving the response message, the object generation unit 41 # A itself returns the response message to the request reception control unit 31 of the request reception unit 3.

The request reception control section 31 receives the response message from the MO class #A that has transmitted the request message, and recognizes that a series of object generation has been completed.

After receiving the response message, the request reception control unit 31 transmits an exclusion confirmation request message to the MO class #A. The exclusion confirmation request message includes the same client ID and message ID as the request message. This exclusive confirmation request message is sent to the exclusive control unit 43 #.
A receives it. Upon receiving the exclusion confirmation request message, the exclusion control unit 43 # A receives the exclusion confirmation request message.
Is given an exclusive search request. This exclusive search request includes the request client ID and the message ID of the exclusive confirmation request message.

The database management unit 44 # A searches the instance status table 44a # A and checks the status value of the instance status list having the request client ID and the message ID included in the exclusion confirmation request (S
6).

If the status value of the instance status list is "queuing", the database management unit 44 #
A detects all the instance status lists based on the request messages of the other clients that are the cause of the queuing, and returns the detected instance status list to the exclusive control unit 43 # A (S6). On the other hand, when the status value of the instance status list is “locked”, the database management unit 44 # A returns an empty instance status list (for example, NULL) to the exclusive control unit 43 # A (S
6). Here, since the status value of the instance status list is “locked”, it is assumed that an empty instance status list (NULL) is returned.

The exclusive control unit 43 # A also transmits an exclusive confirmation request to the exclusive control unit 43 # B of the MO class #B to which the exclusive object detected by the exclusive object detecting unit 42 # A described above belongs.

The exclusive control unit 43 # B is connected to the exclusive control unit 43 # B.
The same processing as in A is executed, and the instance state table 44 is executed.
The instance state list in the "queuing" state is detected from a # B (S7). Also in this case, since the state of the instance state list is “locked”, an empty instance state list is returned to the exclusive control unit 43 # B. The exclusive control unit 43 # B returns the detected instance state list (including the empty list (NULL); hereinafter, referred to as a “detection list”) to the exclusive control unit 43 # A.

The exclusive control unit 43 # A returns the detection list of its own MO class #A and the detection list received from the exclusive control unit 43 # B to the request reception control unit 31. As a result, a series of exclusive confirmation is completed.

The request reception control unit 31 recognizes that the exclusive control has been completed because the detection list is an empty list, and recognizes that the locked instance can be controlled. Thereby, the request reception control unit 3
1 gives the request status management unit 32 a request to change the request status table. The change request includes a request client ID and a message ID for specifying the request state list, and a control start time.

Upon receiving the change request, the request state management unit 32 changes the state value of the request state list corresponding to the request client ID and the message ID included in the change request from "queuing" to "executing". Write the start time included in the change request to the start time of the list (S
8).

Subsequently, the request reception control unit 31 transmits an exclusive control event instructing the start of exclusive control to the exclusive control unit 43 # A of the MO class #A, and starts processing of a request message from the user. A reception response message indicating that the request has been made is transmitted to the requesting client 1. At this stage, the request receiving section 3 can receive and process the next request message from the user.

The reception response message contains the start time and the actual processing time of the request status list. The execution control unit 14 of the request client 1 gives an acceptance response message to the result display unit 12, and the result display unit 12 displays on the display device that the request has been started, the start time, and the actual processing time. Thus, the user can know that the request processing has started, and can know the start time and the end time of the control.

The exclusive control unit 4 that has received the exclusive control event
3 # A executes exclusive control (control indicated by the control ID) for the own class, and performs exclusive control of the exclusive object via the exclusive control unit 43 # B of the MO class #B in which the exclusive object is detected. Execute. Data necessary for control (for example, control ID,
Control arguments and the like) are transmitted from the exclusive control units 43 # A and 43 # B to the transmission device 8 via the device control unit 6, and the network element corresponding to the instance ID is processed (controlled).

When the exclusive control is completed, the exclusive control unit 43 #
A transmits an exclusion release request to the exclusion controller 43 # B of the MO class #B, and also transmits the exclusion release request to the database management unit 44 # A.
To the deletion request. The deletion request includes a request client ID and a message ID for specifying the instance state list. MO that received the exclusion release request
Similarly, the exclusive control unit 43 # B of the class #B sends a deletion request to the database management unit 44 # B. This deletion request also includes the requesting client ID and the message ID.

Database management units 44 # A and 44 #
B deletes (deletes) the instance state list having the requesting client ID and the message ID included in the deletion request from the instance state table (S9, S10), and deletes the instance to be locked next by the deletion (for example, control It detects whether there is a (waiting instance), and if so, changes the instance from the queuing state to the locked state, and transmits an exclusive event to the request receiving unit 3. This exclusive event includes the requesting client ID and the message ID.

Here, it is assumed that there is no instance to be locked due to deletion, and that no exclusive event has been transmitted. The processing when the exclusive event is transmitted will be described later.

The MO class #A transmits an end event indicating that the exclusive control has been completed to the request receiving unit 3. The end event includes the requesting client ID and the message ID that have requested the completed exclusive control. Also, M
The O class #A transmits a request result event to the request client 1. Result display unit 11 of requesting client 1
Displays the received request result on the display device.

Upon receiving the end event, the request receiving unit 3
A deletion request is given to the request state management unit 32. The deletion request includes a request client ID and a message ID for specifying the request status list. The request status management unit 32 deletes the request status list having the request client ID and the message ID included in the deletion request from the request status table (S11).

Object generation units 41 # A and 41 #
B deletes the created object. This allows
The processing of the request information given from the requesting client 1 ends.

In the above operation sequence, MO class #B
Has described the processing when the exclusive object is registered in the locked state. However, the processing when the exclusive object is registered in the queuing state in the MO class #B will be described below.

FIG. 8 is an operation sequence diagram when an exclusive object is registered in a queuing state in MO class #B. The same processes as those in FIG. 7 are denoted by the same reference numerals, and detailed description thereof will be omitted.

The processing (S1 to S3) from when the request message is transmitted from the request client 1 to the request receiving unit 3 until the object creation message is transmitted to the MO classes #A and #B will be described with reference to FIG. Is the same as

The difference from FIG. 7 is that in MO class #B, the same instance ID as the created object is used.
Has already been registered in the instance state table by another message, so that the newly created object is registered as a queuing state in the instance state table (S21).

Thereafter, the object generation unit 41 # B
The response message is transmitted to the MO class #A, and the object generation unit 41 #A transmits the response message to the request reception unit 3.

Subsequently, the request reception control unit 31 transmits an exclusion confirmation request message to the MO class #A. The exclusive control unit 43 # A of the MO class #A that has received the exclusive confirmation request message gives an exclusive search request to the database management unit 44 # A.

The database management unit 44 # A searches the instance state table, and since the searched instance state list is registered as the locked state, the database management unit 44 # A responds with an empty registration list to the exclusive control unit 43 # A (S6). ).
The empty registration list is returned to the request receiving unit 3.

The exclusive control unit 43 # A is a further exclusive object (here, an object of MO class #B)
Sends an exclusion confirmation request message to The processing of MO class #B is the same as that of MO class #A. Here, since the searched instance state list is registered as a queuing state, a registration list by another requesting client which is a queuing factor is responded (S22). The response registration list is transmitted to MO class #A, and exclusive control unit 43 # of MO class #A.
A returns the request to the request receiving unit 3. This completes a series of exclusion checks.

The request reception control unit 31 recognizes that the exclusion has not been completed because a non-empty registration list is returned from the MO class #B. In this case, the request reception control unit 31 transmits a request for generating an object of the screen displaying the registration list to the queuing factor display client 2 as a queuing event, and transmits a reception response message to the request client 1. At this stage, the request receiving unit 3 can process the next request message.

The queuing factor display client 2
The request status from another requesting client that is a queuing factor is displayed, and the requesting client 1 displays on the result display unit 12 that the request processing has been queued.

The MO class #B receives the exclusion release request upon completion of the other exclusive control, changes the next instance to be locked from the queuing state to the locked state, and transmits an exclusive event to the request reception control unit 31. . The exclusive event includes the requesting client ID and the message I
D is included.

The request reception control section 31 gives a search request having the request client ID and the message ID included in the exclusive event to the request state management section 32, and specifies the MO class that is a queuing factor (S23).
Then, the request reception control unit 31 transmits an exclusion confirmation message to the specified MO class (referred to as MO classes #A and #B).

The MO classes #A and #B that have received the exclusion confirmation message search the instance state table (S24, S25), and if the exclusion result is not completed, the request reception control unit 31 does nothing. Here, exclusion is completed.

Upon recognizing that the exclusion has been completed, the request reception control unit 31 gives a change request (including a request client ID, a message ID, and a start time) to the request state management unit 32, and the request state management unit 31. 32 changes the status value of the request status list having the request client ID and the message ID included in the change request from "queuing" to "executing", and writes the start time included in the change request in the request status list ( S26).

The request reception control unit 31 transmits an exclusive control event to the object of the MO class #A, transmits a start event to the requesting client 1, and further transmits a queuing factor display Send a delete request message. The requesting client 1 displays on the result display unit 12 that the request processing has been started.

MO class # that has received the exclusive control event
The exclusive control unit 43 # A of A performs exclusive control on its own class, transmits an exclusive control request message for the object of MO class #B, and executes exclusive control on MO class #B. When the exclusion control is completed, the exclusion control unit 43 # A transmits an exclusion release request for the MO class #B, and the database management unit 44 # A.
To the client (request client ID, message ID). MO class #B that received the exclusion release request
Sends a deletion request (including the requested client ID and the message ID) to the database management unit 44 # B.
The database management units 44 # A and 44 # B delete the corresponding instance state list from the instance state table (S27, S28), and if there is an instance to be locked next by the deletion, queue the instance. The state is changed from the inking state to the locked state, and an exclusive event (including the requesting client ID and the message ID) is transmitted to the request receiving unit 3.

Subsequently, the MO class #A transmits an end event (requested client ID and message ID) to the request receiving unit 3 and transmits a request result event to the requesting client 1. The request client 1 displays the request result on the result display unit 12.

The request reception control unit 31 of the request reception unit 3 that has received the end event gives a deletion request (including the request client ID and the message ID) to the request state management unit 32, and the request state management unit 32 The corresponding request status list is deleted from the status table (S29).
Subsequently, the objects of the MO class #A and the MO class #B are deleted. Thus, a series of exclusive control is completed.

Next, cancellation of the request information input to the request client 1 will be described. FIG. 9 is an operation sequence diagram showing a flow of the cancel processing.

The user wants to cancel the message I
D is designated and the cancel request is sent to the cancel controller 13
Can be entered. The cancellation request input to the cancellation control unit 13 is transmitted from the execution control unit 14 to the request reception unit 3 as a cancellation request message. The cancel request message includes a request client ID and a message ID for specifying the request message to be canceled.

The request reception control unit 31 of the request reception unit 3 receives and processes the cancel request message. When there are a plurality of cancel request messages from a plurality of requesting clients 1, like the control request message,
Only the cancellation request message from one requesting client 1 is received, and after the processing of the cancellation request message is completed, the next cancellation request message is received.

The request reception control section 31 sends a request for searching the request state list having the request client ID and the message ID included in the cancel request message to the request state management section 32 (S21).

The request reception control unit 32 determines whether or not the status value of the retrieved request status list is "queuing". If the status value is "queuing", the request reception control unit 32 has the MO class ID of the request status list. MO class (here M
O class #A. ) Is transmitted (S31). Request client ID included in the cancel request message is included in the exclusion release request message
And a message ID.

When the status value of the retrieved request status list is “executing” or when the request status list has already been deleted and no longer exists, the request reception control unit 31
The requesting client 1 is informed that the request cannot be canceled and the reason therefor. Result display unit 12 of requesting client 1
Displays on the display device that cancellation is not possible and the reason therefor, and notifies the user.

Upon receiving the exclusion release request message, the exclusion control unit 43 # A of the MO class #A issues a request to delete the instance state list having the request client ID and the message ID included in the exclusion release request message to the database management unit 44 #. Give to A. Thereby, the database management unit 44 # A deletes the instance status list for which the deletion request has been made from the instance status table 44a # A (S32).

The exclusive control unit 43 # A starts the exclusive object detection unit 4 when the instance status list to be deleted from the instance status table 44a # A is registered.
As for the other exclusive object searched by 2 # A, an exclusive release request message for deleting the instance state list of the exclusive object is transmitted to the MO class (MO class #B) to which the exclusive object belongs. I do. This lock release request message includes
The request client ID and the message ID are included.

MO class #B that has received the exclusion release request
Sends a deletion request including the requested client ID and the message ID to the database management unit 44 # B, and the database management unit 44 # B deletes the instance status list having the requested client ID and the message ID from the instance status table 44a # B. Yes (S3
3).

Database management units 44 # A and 44 #
B deletes the instance state list from the instance state table and determines whether there is an instance to be newly locked by the deletion, and if so, changes the instance from the queuing state to the locked state. Then, the exclusive event (including the requesting client ID and the message ID) is transmitted to the request receiving unit 3.

When the exclusion release is completed, the exclusive control unit 43 #
A responds to the request reception control unit 31 with the result, and the request reception control unit 31 issues a deletion request (including the request client ID and the message ID) to the request state management unit 32. The request status list is deleted from the request status table (S34).

Finally, the request receiving unit 3 sets the MO class #A
And the object deletion message of #B is transmitted, and the result of the cancel request is returned to the requesting client 1.
The MO classes #A and #B delete the objects of the deleted event state list, respectively, and the requesting client 1 displays the request result on the result display unit 12. Thus, the cancel processing ends.

Next, a description will be given of a process of searching for an instance serving as a queuing factor using the queuing factor display client 2. FIG. 10 is an operation sequence diagram of a search process of an instance that is a queuing factor.

The queuing factor display client 2 receives a queuing factor search request from the user, and the queuing factor search unit 22 sends a queuing factor search request message to the request receiving unit 3 (including a request client ID and a message ID). Send

The request reception control unit 31 of the request reception unit 3 sequentially receives the queuing factor search request messages one by one, and requests the queuing factor search request for the request status list having the request client ID and the message ID included in the request message. This is given to the state management unit 32. As a result, the corresponding request state list is searched, and the MO class (here, MO class #A) included in the searched request state list is searched.
And ) Is specified (S41). Request reception control unit 3
1 transmits an exclusion confirmation message to the specified MO class #A.

Upon receiving the exclusion confirmation message, the exclusion control unit 43 # A of the MO class #A sets the database management unit 44.
#A is given an exclusive search request (including the requesting client ID and the message ID). Database management unit 4
4 # A is the requesting client I included in the exclusive search request.
D and an instance state list having the message ID are retrieved from the instance state table (S4).
2).

When the status value of the retrieved instance status list is “queuing”, the exclusive control unit 43
#A detects all the registration lists of the other requesting clients 1 that are causing the queuing, and responds to the request reception control unit 31. If the status value of the retrieved instance status list is “locked”, the exclusive control unit 43
#A returns an empty registration list to the request reception control unit 31.

The exclusive control unit 43 # A further performs another exclusive object (here, an object of MO class #B).
The exclusive control unit 43 # B of the MO class #B transmits the registration list or the empty registration list to the exclusive control unit 43 # A in the same manner as the exclusive control unit 43 # A. Return (S43). This completes a series of exclusion checks.

The exclusive control unit 43 # of the MO class #A
A compares the registration list detected by itself as a queuing factor with the registration list detected in MO class #B, and if there is a list having the same request client ID and message ID, These lists are combined into one, and a response is made to the request reception control unit 31.

The request reception control section 31 gives a queuing factor search request (including a registration list) to the request status management section 32 based on the response result, and, based on the request status table 32a, the requesting client which is the queuing factor. Search request information and display the queuing factor display client 2
Responds to the retrieved request status.

The queuing factor display client 2
The request status (search result) given from the request reception control unit 31 is displayed on the queuing factor display unit 21. FIG.
Shows an example of a display screen by the queuing factor display client. A list of control requests and a queuing factor for the control requests is displayed. The list includes the actual processing time and the scheduled completion time. The actual processing time is the same as that stored in the request status table. The scheduled completion time is a time obtained by adding the substantial processing time to the start time of the request state table, and
2 or calculated by the queuing factor display unit 21.

Thus, the latest queuing factor is displayed. Thus, the queuing factor display process ends. The queuing factor display unit 21 can display the request states in the order of the reception times based on the reception times in the request state table.

As described above, the user can confirm what state the request registered in the queuing state is currently in. As a result, the total execution time including the queuing time can be predicted.

[0142]

According to the present invention, the occurrence of deadlock can be prevented, and the user does not need to input a control request again after a timeout.

Further, according to the present invention, when a control request is queued, it is possible to display request information from another requesting client which is a cause of queuing, and to estimate the total execution time. The user does not have to wait for a long time without knowing when to complete. Further, the user can confirm the queuing state and cancel his / her request message as necessary, or can cancel the request message of another user and then perform priority processing of his / her request message.

[Brief description of the drawings]

FIG. 1 is a functional block diagram showing an overall configuration of an operation system 10 according to an embodiment of the present invention.

FIG. 2 is a functional block diagram showing a detailed configuration of a requesting client.

FIG. 3 shows the structure of a request message.

FIG. 4 is a functional block diagram showing a detailed configuration of a queuing factor display client.

FIG. 5 is a functional block diagram illustrating a detailed configuration of a request receiving unit.

FIG. 6 is a block diagram showing a detailed configuration of an MO class.

FIG. 7 is an operation sequence diagram of the operation system.

FIG. 8 is an operation sequence diagram of the operation system.

FIG. 9 is an operation sequence diagram of the operation system.

FIG. 10 is an operation sequence diagram of the operation system.

FIG. 11 shows an example of a display screen by a queuing factor display client.

FIG. 12 is a physical implementation diagram of a transmission device of the communication network system and a logical model diagram in which the transmission device is modeled by an object-oriented model.

FIG. 13 is a functional block diagram showing a configuration of a conventional operation system.

FIG. 14 shows management data of network components;
(A) shows the instance state table of the MO class of the unit, and (B) shows the instance state table of the MO class of the package.

FIG. 15 is an operation sequence diagram showing occurrence of deadlock in a conventional operation system.

[Explanation of symbols]

Reference Signs List 10 Operation system 1 ₁ to 1 _n Request client 2 Queuing factor display client 3 Request accepting unit 4 ₁ to 4 ₃ MO class 5 _{1 to} 5 ₃ Database 8 ₁ to 8 _m Transmission device 31 Request accepting control unit 32 Request state managing unit 41 object generation unit 42 exclusive object detection unit 43 exclusive control unit 44 database management unit

   ────────────────────────────────────────────────── ─── Continuation of front page    (72) Inventor Naoyuki Tosa             2-3-9 Shin-Yokohama, Kohoku-ku, Yokohama-shi, Kanagawa             No. Fujitsu Digital Technology Stock Association             In-house (72) Inventor Tsuyoshi Naka             2-3-9 Shin-Yokohama, Kohoku-ku, Yokohama-shi, Kanagawa             No. Fujitsu Digital Technology Stock Association             In-house (72) Inventor Hideyuki Sora             2-3-9 Shin-Yokohama, Kohoku-ku, Yokohama-shi, Kanagawa             No. Fujitsu Digital Technology Stock Association             In-house (72) Inventor Minori Kofu             2-3-9 Shin-Yokohama, Kohoku-ku, Yokohama-shi, Kanagawa             No. Fujitsu Digital Technology Stock Association             In-house F term (reference) 5B098 AA09 AA10 GA02 GD07 GD16                       GD27

Claims (5)

[Claims] An operation system for controlling a transmission device constituting a communication network system and a network component including a device constituting the transmission device, comprising: a control request input unit for inputting a control request for the network component; A request receiving unit that receives a control request input to the control request input unit, a state of a first network component that is a target of the control request received by the request receiving unit, and a status of the first network component. Along with the control, the state of the second network element for which control by another control request is required to be eliminated is set to a lock state indicating the exclusion of control by another control request or to the end of control by another control request. A storage unit for storing as a queuing state shown, and each of the first and second network components When the state of the same network element is already stored in the storage unit, the state is stored in the storage unit as a queuing state, and when not stored, the state is stored as a locked state in the storage unit. And a storage management unit that erases the state from the storage unit when control is completed, wherein the request reception unit is configured to store the state of the state by the storage management unit in response to the control request received by the request reception unit. An operation system for receiving a next control request from the control request input unit after the storage is completed. 2. The method according to claim 1, wherein the first or the second
An operation system further comprising a queuing factor display unit for displaying another control request that is a cause of the queuing state when the state of the network component is stored as the queuing state in the storage unit. 3. The queuing state according to claim 1, wherein the state of the first or second network element is stored in the storage unit as the queuing state. A queuing factor search unit that receives a search request for another control request and searches for another control request that is a cause of the queuing state based on the received search request; A queuing factor display section to be displayed,
An operation system further comprising: 4. The storage unit according to claim 1, wherein the state of the first or second network element is stored in the storage unit as the queuing state. An operation system further comprising: a cancel control unit that receives a cancel request for erasing a state of a first or second network element and deletes a state from the storage unit based on the received cancel request. 5. An exclusive control method of an operating system for controlling a transmission device constituting a communication network system and a network component including the device constituting the transmission device, the method comprising controlling the network component inputted by a user. A request for receiving a request, a first network component to be the target of the received control request, and a second network component which needs to exclude control by another control request in accordance with the control of the first network component. If the state of the same network element is already stored in the storage unit for storing the state of the network element for each of them, the state is changed to a queuing state indicating the end of control by another control request. Is stored in the storage unit as above, and if not stored, other control is performed. A lock state indicating the exclusion of control by a request is stored in the storage unit, and after the storage processing of the received control request in the storage unit is completed, a next control request from a user is received, and 1
And an exclusive control method, wherein when the control of the second network element is completed, the state is deleted from the storage unit.