KR101639912B1 - Event managing system of steel process middleware - Google Patents

Abstract

The event management system of the steel process middleware according to an embodiment of the present invention includes a timer manager managing a target task number, a timer ID and a timer according to a timer registration request of a registered task; A timer information manager for selecting a timer closest to the event time; A timer execution manager for generating a time event when an event time of the selected timer is reached; And a timer event manager for managing the waiting task number of the waiting task waiting for the time event and delivering the time event to the waiting event queue.

Description

{EVENT MANAGING SYSTEM OF STEEL PROCESS MIDDLEWARE}

The present invention relates to an event management system of a steel process middleware.

The role of middleware in the steel process control work is to manage the tasks currently performed by performing tasks such as storing and referencing information related to communication or process control between tasks in response to a task request.

In general, steel process middleware has the feature that the creation and deletion of a large number of tasks are repeatedly performed, and when a new service is added, a new service function added to the middleware is added. Because of this feature, steel process middleware should be able to efficiently allocate task resources according to the dynamic situation, efficiently manage the resources of the system in which middleware is executed, and increase the overall performance of the executed system. In addition, steel process middleware should be easy to add new service functionality in terms of middleware developers.

Modularity of the structure of the middleware system that can accommodate the availability of the middleware and the possibility of changes due to the process is needed because the required service and responsiveness, system platform, and distributed environment requirements required by the steel process are various.

In addition, since the steel process includes important processes such as heat treatment, water treatment, tracking, and performance collection in a continuous process due to its characteristics, optimization and standardization of a time event processing method, which is one of services for steel processing, is required.

Korean Patent Publication No. 10-2010-0076840

There is a need for a time management system for mediating time event management in steel process middleware, optimizing the processing method of time events, and providing a standardized time event service.

The event management system of the steel process middleware according to an embodiment of the present invention includes a timer manager managing a target task number, a timer ID, and a timer according to a timer registration request of a registered task; A timer information manager for selecting a timer closest to the event time; A timer execution manager for generating a time event when an event time of the selected timer is reached; And a timer event manager for managing the waiting task number of the waiting task waiting for the time event and delivering the time event to the waiting event queue.

The event management system of the steel process middleware according to the embodiment of the present invention can optimize the time event processing method and provide the standardized time event service.

1 is a block diagram illustrating an event management system of a steel process middleware according to an embodiment of the present invention.
2 is a flowchart illustrating a timer registration processing procedure according to an embodiment of the present invention.
3 is a flowchart illustrating a time event generation and delivery procedure according to an embodiment of the present invention.
4 is a flowchart illustrating an event service request processing procedure according to an embodiment of the present invention.

Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings.

However, the embodiments of the present invention can be modified into various other forms, and the scope of the present invention is not limited to the embodiments described below. Further, the embodiments of the present invention are provided to more fully explain the present invention to those skilled in the art. It should be understood that the various embodiments of the present invention are different, but need not be mutually exclusive. For example, certain features, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the invention in connection with an embodiment.

Also, to "include" an element means that it may include other elements, rather than excluding other elements, unless specifically stated otherwise.

The term " manager " used in this embodiment means a hardware component such as software or an FPGA (field-programmable gate array) or ASIC, and the 'manager' performs certain roles. However, 'manager' is not meant to be limited to software or hardware. The '~ manager' may be configured to reside on an addressable storage medium and may be configured to play one or more processors. Thus, by way of example, 'to manager' may refer to components such as software components, object-oriented software components, class components and task components, and processes, functions, attributes, , Subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and '~ administrators' may be further combined into a smaller number of components and '~ administrators' or further components and '~ administrators'. In addition, components and 'managers' may be implemented to play one or more CPUs in a device or system.

1 is a block diagram illustrating an event management system of a steel process middleware according to an embodiment of the present invention.

Referring to FIG. 1, an event management system of a steel manufacturing middleware according to an embodiment of the present invention includes a timer manager 210, a timer information manager 270, a timer execution manager 280, and a timer event manager 310 .

The timer manager 210 can manage to store the target task number and the timer ID according to the timer registration request of the registered task 11.

The registration task 11 is a software task for registering a timer for generating a time event. The timer to register may be available to the registered task 11 or another task.

Here, task-service handlers 101 to 104, which are substitute processing modules for ensuring a fast response time in response to a service request (for example, a timer registration request) requested by an application software task, can be allocated one-by-one for each task.

Also, the timer information manager 270 may select a timer closest to the event time, and the timer execution manager 280 may generate a time event when the event time of the selected timer is reached.

The timer event manager 310 manages to store the waiting task number of the waiting task waiting for the time event, and can forward the time event to the event waiting queue.

In addition, the event management system of the steel process middleware according to an embodiment of the present invention includes a target task number manager 220 and a target task number pool 240. A timer ID manager 230, a timer ID pool 250, and a task-timer mapper 260. The timer-

The target task number manager 220 may generate the target task numbers 241 to 24N and store the target task numbers 241 to 24N in the target task number pool 240.

The target task number pool 240 may include the target task numbers 241 to 24N and may have a structure capable of adding, deleting, and searching the target task numbers 241 to 24N.

The timer ID manager 230 generates the timer IDs 251 to 25N according to the timer ID setting document 230-1 and outputs the timer IDs 251 to 25N to the timer ID pool 250, Lt; / RTI >

The timer ID pool 250 includes the timer IDs 251 to 25N and may have a structure capable of adding, deleting, and searching the timer IDs 251 to 25N.

The task-timer mapper 260 generates task-timer mapping information in which the target task numbers 241 to 24N and the timer IDs 251 to 25N are mapped and outputs the task-timer mapping information to the timer manager (210).

In addition, the event management system of the steel process middleware according to an embodiment of the present invention may include a timer pool 290.

The timer pool 290 includes timers 291 through 294 and may have a structure that allows the timers 291 through 294 to be added, deleted and retrieved by the timer information manager 270.

Also, the timer information manager 270 may add, delete, and search the timers 291 to 294 included in the timer pool 290 according to the timer registration setting document 370-1.

In FIG. 1, the timers 291 to 294 are shown one by one according to the types of timers (e.g., daily, delay, period, and one time), but the timer pool 290 may include a plurality of timers of the same type.

The timer manager 210 can manage to modify the timer in response to the timer replacement request of the replacement task 12 and delete the target task number, the timer ID, and the timer in accordance with the request of the deletion task 13 Can be managed.

Specifically, the timer manager 210 can retrieve the task-timer mapping information provided by the task-timer mapper 260 when a request for the replacement task 12 is received, The task-timer mapping information may be modified through the task-timer mapper 260 and the timer may be modified through the timer information manager 270. [

Also, the timer manager 210 can retrieve the task-timer mapping information provided by the task-timer mapper 260 when a request for the deletion task 13 is received, The timer ID, the task-timer mapping information, and the timer for which the deletion is requested can be deleted.

In addition, the event management system of the steel process middleware according to an embodiment of the present invention includes a waiting task number manager 320, a waiting task number pool 340, and the like. An event waiting queue manager 330, an event waiting queue pool 350, and a task-event mapper 360. The event-

The waiting task number manager 320 may generate waiting task numbers 341 to 34N and store the waiting task numbers 341 to 34N in the standby task number pool 340.

The standby task number pool 340 may include the waiting task numbers 341 to 34N and may have a structure capable of adding, deleting, and searching the waiting task numbers 341 to 34N.

The event waiting queue manager 330 may generate event waiting queues 351 to 35N and store the event waiting queues 351 to 35N in the event waiting queue pool 350. [

The event wait queue pool 350 may include the event wait queues 351 to 35N and may have a structure capable of adding, deleting, and searching the event wait queues 351 to 35N.

The task-event mapper 360 generates task-wait queue mapping information in which the wait task numbers 341 to 34N and the event wait queues 351 to 35N are mapped, To the timer event manager (310).

In addition, the event management system of the steel process middleware according to an embodiment of the present invention may include a time event manager 370 and a time event pool 380.

The time event pool 380 may include time events 381 to 384 and may have a structure capable of adding, deleting, and retrieving the time events 381 to 384.

In addition, the time event manager 370 may add, delete, and retrieve the time events 381 to 384 included in the time event pool 380 according to the time event setting document 360-1.

Although FIG. 1 shows time events 381 to 384 one by one according to types of time events (e.g., daily, delay, period, one time), the time event pool 380 includes a plurality of time events of the same kind .

Accordingly, since the timer for generating the time event and the management structure for the time event generated by each timer can be binarized, it is possible to simultaneously perform timer addition / deletion and time event generation / deletion, thereby optimizing the performance, Event part can be managed separately.

Therefore, according to the event management system of the steel process middleware according to the embodiment of the present invention, a time event processing method can be optimized and a standardized time event service can be provided.

2 is a flowchart illustrating a timer registration processing procedure according to an embodiment of the present invention.

First, when a service of the event management system according to an embodiment of the present invention is started, a timer manager 210 (FIG. 1) may be created (S210).

When the timer manager is created, the timer manager may generate a timer execution manager 280 (FIG. 1) (S310) and generate a timer event manager 310 (FIG. 1) (S410).

When the registration task is started and the timer registration is requested (S201), the timer manager can follow the timer registration request (S220) and confirm the task-timer mapping information (S230).

The timer manager determines whether there is task-timer mapping information for the timer requested for registration (S230). If there is no task-timer mapping information for the requested timer, the timer manager can generate task-timer mapping information (S250). If the task-timer mapping information for the requested timer exists, the task-timer mapping information may be changed (S255).

Then, the timer manager can transmit the timer registration completion to the registration task (S260), and the registered task having received the timer registration request can receive the completion of the timer registration request (S209) and can be terminated.

3 is a flowchart illustrating a time event generation and delivery procedure according to an embodiment of the present invention.

First, after the timer execution manager 280 (FIG. 1) is generated (S310), the timer information manager 330 (FIG. 1) may select a timer closest to the event time (S320).

Thereafter, the timer execution manager can confirm whether the event time of the selected timer has been reached (S330).

If the event time has not been reached, it is waited for the arrival of the event time (S340). If the event time is reached, a time event can be generated (S345).

Next, it is determined whether there is a waiting task waiting for the time event (S350). If there is the waiting task, a time event can be delivered to the waiting event queue (S365).

If the waiting task does not exist, the task-event mapping information is checked (S360), and it is determined whether mapping information exists (S370).

If the mapping information exists, the event waiting queue is found and the time event is transmitted (S380). If the mapping information does not exist, the task-event mapping information may be generated and the time event may be transmitted (S385).

Finally, the timer manager 210 (FIG. 1) may delete information related to the timer if the selected timer is a one-time use (e.g., delay, one-time) timer.

4 is a flowchart illustrating an event service request processing procedure according to an embodiment of the present invention.

First, when a receiving task is started and an event service is requested after the timer event manager 310 (FIG. 1) is created (S401), the timer event manager can be executed according to the event service request (S420) The event mapping information can be confirmed (S430).

Thereafter, the timer event manager determines whether there is task-event mapping information (S440). If there is task-event mapping information, the timer event manager checks the state of the event wait queue (S450) (S460).

If there is no time event already generated, the event wait queue can wait for the occurrence of the time event (S470).

In contrast, if there is no task-event mapping information, the timer event manager can generate task-event mapping information (S455).

Thereafter, the event wait queue can wait for occurrence of a time event (S470).

If a time event has already occurred or a time event is delivered to the event waiting queue (S365), the timer event manager can transmit a time event to the waiting task (S480).

Finally, the receiving task receives the completion of the event service request (S409) and can be terminated.

Accordingly, even if the time event generated by the timer is not missed and is delivered to the event wait queue so that the application software can not receive the event but is terminated, the re-executed application software is not processed and the time event is received Can be done.

Therefore, according to the event management system of the steelworks middleware according to the embodiment of the present invention, a time event service in which the time event processing method is stabilized can be provided.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not intended to limit the invention to the particular forms disclosed. It will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the invention as defined by the appended claims.

210: Timer Manager
220: Destination task number manager
230: Timer ID manager
240: Target task number pool
250: Timer ID Pool
260: Task - Timer Mapper
270: Timer Information Manager
280: Timer execution manager
310: Timer Event Manager
320: Standby task number manager
330: Event Waiting Queue Manager
340: Standby task number pool
350: Event Waiting Queue Pool

Claims (10)

A timer manager for managing a timer to register a target task number and a timer ID (ID) in accordance with a timer register request of the registered task;
A timer information manager for selecting a timer closest to the event time;
A timer execution manager for generating a time event when an event time of the selected timer is reached; And
A timer event manager for managing the waiting task number of the waiting task waiting for the time event and for delivering the time event to the waiting event queue;
The event management system of the steel process middleware.
The method according to claim 1,
A target task number pool including the target task number;
A target task number manager for generating the target task number and storing the target task number in the target task number pool;
A timer ID pool including the timer ID; And
A timer ID manager for generating the timer ID and storing the timer ID in the timer ID pool;
The event management system of the steel process middleware.
The method of claim 2,
And a task-timer mapper for generating task-timer mapping information in which the target task number and the corresponding timer ID are mapped and providing the task-timer mapping information to the timer manager.
The method according to claim 1,
Wherein the timer manager manages a timer to be modified according to a timer replacement request of a replacement task.
The method according to claim 1,
The timer manager deletes a target task number and a timer ID according to a timer deletion request of the deletion task. And the timer is managed to delete the event management system of the steel process middleware.
The method according to claim 1,
A waiting task number pool containing the waiting task number;
A target task number manager for generating the standby task number and storing the standby task number in the standby task number pool;
An event wait queue pool including the event wait queue; And
An event wait queue manager for generating the event wait queue and storing the event wait queue in the event wait queue pool;
The event management system of the steel process middleware.
The method of claim 6,
And a task-waiting queue mapper for generating task-waiting queue mapping information in which the waiting task number and the corresponding event waiting queue are mapped and providing the task-waiting queue mapping information to the timer event manager. Event management system.
The method according to claim 1,
Wherein the timer event manager manages to store the waiting task number according to an event service request of the receiving task and assigns an event waiting queue to the waiting task.
The method according to claim 1,
And a timer pool having a structure capable of adding, deleting and searching timers by the timer information manager.
The method according to claim 1,
A time event pool having a structure capable of adding and deleting time events generated through the timer execution manager; And
The time event manager managing the time event pool
The event management system of the steel process middleware.

Images