CN108140008A - Steel handles the Event Service method and frame system of middleware - Google Patents
Steel handles the Event Service method and frame system of middleware Download PDFInfo
- Publication number
- CN108140008A CN108140008A CN201680062015.8A CN201680062015A CN108140008A CN 108140008 A CN108140008 A CN 108140008A CN 201680062015 A CN201680062015 A CN 201680062015A CN 108140008 A CN108140008 A CN 108140008A
- Authority
- CN
- China
- Prior art keywords
- event
- subscription
- task
- service
- information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/76—Architectures of general purpose stored program computers
- G06F15/82—Architectures of general purpose stored program computers data or demand driven
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/4881—Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
- G06Q50/04—Manufacturing
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Abstract
The Event Service method of steel processing middleware according to the embodiment of the present invention is the Event Service method of the steel processing middleware by mission application software and Events Frame execution, the mission application software includes allowing Application Programming Interface (API) library of task requests Event Service, wherein, this method includes the following steps：Service processor responds Event Service request；Information is defined based on the event for defining event id and size of data to generate event；And if information and the information match of subscription event that pulls subscription about the event generated, the event generated is sent to the subscription task for being mapped to subscription event according to the mapping data of task manager as subscription event.
Description
Technical field
Present disclosure is related to the Event Service method and frame system of steel processing middleware.
Background technology
Function of the middleware in steel processing control is in response to such as store and join to perform in the request sent out by task
Examine times that the processing of the information about the information of the communication between task or about processing control and management are currently running
Business.
Such task can be application software, and the independent factory's control function for being exclusively responsible for segmentation is to improve
The performance and stability of system.
In addition, in order to cooperate, task can indicate that middleware creates event and can receive by another task creation
Event.
The thing that the steel of the relevant technologies handles middleware is handled by sending and receiving message with one-to-one communication mode
Part service, therefore, when task must send event to multiple tasks, it may be necessary to extended processing time.
In addition, steel processing middleware repeatedly creates/deletes the multi-task, and when adding new cooperative system, it must
The Event Service function of new cooperative system must be added in steel processing middleware.
The developer for handling middleware for steel therefore, it is necessary to frame system provides to develop Event Service method and processing
And the environment safeguarded according to new cooperative system.
Invention content
Technical problem
One side in the present disclosure can provide a kind of frame system, which is configured to improve in steel processing
Between part Event Service processing speed and optimization processing exploitation and management environment.
In addition, when compatibility when handling Event Service, can be kept by sending and receiving message.
Technical solution
According to one side in the present disclosure, can provide by the steel processing of mission application software and Events Frame execution
Between part Event Service method, the mission application software include permission task send out Event Service request Application Programming Interface
(API) library.Event Service method can include：Service processor responds Event Service request；Based on definition event id
Information is defined with the event of size of data to create event；And if about the event created information with about being asked
Subscription event information it is consistent, then according to the mapping data of task manager using the event created as requested subscription
Event is sent to the subscription task for being mapped to requested subscription event.
According to another aspect in the present disclosure, a kind of Event Service frame system of steel processing middleware can be provided,
The Event Service frame system realized by least one processor and including mission application software and Events Frame, which should
With the API library for the Event Service that software includes task requests is allowed to include event subscription.Events Frame can include：Service processing
Device is configured to respond Event Service request；Task manager is configured to management and defines event id and data
The event of size defines information and manages the mapping number that wherein requested subscription event is mapped to corresponding subscription task
According to；And event scheduling interface, wherein, if the information about the event for defining information creating based on event by service processor
Consistent with the information about requested subscription event, then event scheduling interface can be using the event created as requested
Subscription event is sent to subscription task.
Advantageous effect
According to the embodiment of the present disclosure, Event Service method and frame system can improve steel processing middleware
The processing speed of Event Service and the efficient processing exploitation of offer and management environment.
Description of the drawings
Fig. 1 (a) is the exemplary schematic diagram for the Event Service for showing processing steel processing middleware.
Fig. 1 (b) is the Event Service frame using steel processing middleware shown according to the embodiment of the present disclosure
The schematic diagram of the Event Service processing procedure of system.
Fig. 2 is the frame for the Event Service frame system for showing steel processing middleware according to the embodiment of the present disclosure
Figure.
Fig. 3 be show according to the embodiment of the present disclosure steel processing middleware Event Service frame system should
With the table in programming interface (API) library.
Fig. 4 is the Event Service frame system in steel processing middleware specifically illustrated according to the embodiment of the present disclosure
The block diagram for the Events Frame that system includes.
Fig. 5 is the Event Service frame system for showing to handle middleware according to the steel of another embodiment in the present disclosure
Block diagram.
Fig. 6 is the block diagram for the memory interoperability services for showing frame system processing as shown in Figure 5.
Fig. 7 is the flow chart for showing memory interoperability services shown in Fig. 6.
Fig. 8 is to show that the processing event in Event Service frame system that is used for according to the embodiment of the present disclosure is created
Build the sequence diagram of the processing of request.
Fig. 9 is to show that the processing event in Event Service frame system that is used for according to the embodiment of the present disclosure connects
Receive the sequence diagram of the processing of request.
Specific embodiment
Illustrative embodiments in the present disclosure are described in detail with reference to the accompanying drawings.
However, present disclosure can be illustrated in many different forms, and present disclosure is not necessarily to be construed as
It is limited to specific embodiment described herein.
It will be further appreciated that term " comprising " and/or "comprising" used herein show there is stated spy
Sign or component, but do not precluded the presence or addition of other one or more features or component.
In the following embodiments, suffix "-er " or "-or " are used to indicate the software or hardware component for performing certain tasks
Such as field programmable gate array (FPGA) or application-specific integrated circuit (ASIC).However, suffix "-er " or "-or " are not limited to
Software or hardware component.This component with suffix "-er " or "-or " may be configured to reside in addressable storage medium
Above or it is configured to perform one or more processors.Therefore, this component with suffix "-er " or "-or " shows
Example can include component software, the component of the component software of object-oriented, such as class component and task component, processing, function, category
Property, process, subroutine, program code segments, driver, firmware, microcode, circuit system, data, database, data structure, table
Lattice, array and variable.Being there is provided in the component and other assemblies with suffix "-er " or "-or " can be combined into
Less component is further divided into additional component.In addition, component with suffix "-er " or "-or " and other
Component may be implemented so that these components can perform one or more CPU in equipment or system.
Fig. 1 (a) is the exemplary schematic diagram for the Event Service processing procedure for showing steel processing middleware, and Fig. 1 (b) is to show
The Event Service of the Event Service frame system using steel processing middleware according to the embodiment of the present disclosure processes
The schematic diagram of journey.
With reference to Fig. 1 (a), steel processing middleware can handle Event Service by one-to-one communication means.
In detail, when task (A) sends event into multiple tasks B1 to BN, middleware is in response to from task A's
Event creates instruction and creates event and send event into task B1, refers to then in response to the event establishment from task A
It enables establishment event again and sends event into task B2.The processing can be repeated, is appointed until middleware is sent event into
Until business BN.
On the contrary, with reference to 1 (b), taken in the event using steel processing middleware according to the embodiment of the present disclosure
It is engaged in the event handler procedure of frame system, task A only once generates event and creates instruction, and then middleware can be processed in batches
For all traffic controls of task A.
Therefore, can be had using the steel of the Event Service frame system of embodiment in the present disclosure processing middleware
The Event Service processing speed of raising.
Fig. 2 is the frame for the Event Service frame system for showing steel processing middleware according to the embodiment of the present disclosure
Figure.
With reference to Fig. 2, the steel processing middleware of present embodiment can include mission application software 10 and Events Frame 20.Appoint
Application software 10 of being engaged in can include multiple tasks 11 to 1N and Application Programming Interface (API) library 100.Events Frame 20 can wrap
Multiple service processors 21 are included to 2N, task manager 200 and event scheduling interface 300.
In addition, according to design, Events Frame 20 can include at least one of the following：Sent event queue pond 400,
Event Service monitor 500, frame manager 600 and storage device 30.
Multiple tasks 11 to 1N can be include for operate steel processing 2 grades of systems steel processing operation logic it is multiple
Application software, and each in task 11 to 1N can call the API for the Event Service for being exclusively used in Events Frame 20 to connect
Receive Event Service.Herein, middleware, and 1 grade, 2 grades and 3 are handled using task 11 to 1N, steel for 2 grades of systems of steel processing
Grade system composition steel processing automated system.
For steel processing 1 grade of system be connected to steel mill production processing rudimentary other places execution unit equipment control,
Sequential control and PID control.For this purpose, 1 grade of system for steel processing can include programmed logic controller (PLC), distribution
Control system (DSC), digital self-operated controller (DDC), sensor etc..
In addition, 3 grades of systems for steel processing can be set for contract/order management, production/processing management and quality
The operation system of meter, and Enterprise Resources Plan (ERP) system and manufacturing execution system (MES) can be included.
API library 100 be according to as using middleware services performing the request of the task of the primary proxy of logical process and
One group of called programming function, and each task can call corresponding API to include event to the request of Events Frame 20
The various services of service.
API library 100 can include API, and task can include event definition, event by API to the request of Events Frame 20
Subscription, event subscription cancellation, event establishment, event reception and event define the Event Service of deletion.Later with reference to Fig. 3 according to
Embodiment describes the specific API that API library 100 can include.
It is asked in response to the Event Service of the API of mission application software 10, multiple service processors 21 can be distributed to 2N.
Task manager 200 can be defined information with management event and can manage subscription event and correspondence about request
Subscription task between mapping data.Herein, statement " management something or other " refers to create, delete and change the things.
Herein, event defines information including event identifier (ID) and about the thing that can be sent to from task for handling Event Service
The data information of the variable data of part frame 20 (referring to Fig. 2).Herein, data information can be with the size of indicator variable data.
In addition, task manager 200 can define information and mapping number in response to the request of service processor 21 to 2N to provide event
According to.
If creating subscription event, subscription event can be sent to by event scheduling interface 300 according to mapping data
Corresponding subscription task.
Sent event queue pond 400 can include it is multiple sent event queue, it is the multiple to have sent event queue
It waits for until subscription task receives the subscription event sent by event scheduling interface 300.
Event Service monitor 500 can monitor task manager 200, event scheduling interface 300 and send event team
Pond 400 is arranged, the information related with the state for subscribing to event is sent to mission application software 10.
When Events Frame 20 works, frame manager 600 is created first, and frame manager 600 can be initial
Change all components that processing creates Events Frame 20 later, and when Events Frame 20 is stopped, frame manager 600 can
To collect the resource for the component for distributing to Events Frame 20.
Storage device 30 can store setting data list 31, which is to include to control event box
The file data of the setting value of the processing of the component of frame 20.In addition, setting data list 31 can be included comprising about subscription thing
The event system information of the event setting value of part and subscription task and mapping data.
Task manager 200, event scheduling interface 300 are described later with reference to Fig. 4 and have sent event queue pond 400
Specific example.
Fig. 3 is the Event Service frame system for showing steel processing middleware according to the embodiment of the present disclosure
The table of API library.
With reference to Fig. 3, API library can include with the API of request event service, the Event Service can including：Event definition,
Event subscription, event subscription cancellation, event creates, event receives, event defines deletion, the event that has sent but not yet received
Number specific to task, the event for having sent but not yet having received specific to task list, subscribe to event specific to appointing
The list of business, the addition set specific to the list of event, the initialization for having sent event queue, event of subscription task, thing
The deletion of part setting, the addition of event subscription task setting, the deletion of event subscription task setting and event system setting.
Hereinafter, the function of API being described one by one.Event definition (can be referred in Fig. 2 with command event manager
Reference numeral 200) it is created for determining that the Events Frame of the cooperation between task (referring to the reference numeral 20 in Fig. 2) is middle
Event defines information.Herein, event defines information and includes event id and about can be sent to handle event from task
The data information of the variable data of the Events Frame (referring to the reference numeral 20 in Fig. 2) of service.Herein, data information can be with
The size of indicator variable data.
Event subscription can create the information about the requested subscription event of subscription task with command event frame.If it closes
Consistent with the information about the event of subscription in the information of the event of establishment, then subscription event can be sent to subscription by Events Frame
Task.
Event subscription is cancelled with command event frame to cancel is not required subscription for performing the task of logical process
The subscription of event.
Event creates based on event can define information to create event with command event frame, and by event id and correlation
Variable data be sent to subscription task.Event is created defines letter using the event being defined on by event defined in Events Frame
Breath.That is, each event created by event and a plurality of event created in Events Frame are defined in information
It is consistent that one event defines information, so as to event id and corresponding size of data.
Event, which receives, subscription task to be notified to be in the standby for receiving subscription event to Events Frame.
Event is defined deletion and can be defined with the subscription event information of command event frame deletion event frame management and event
Information.
The number specific to task for the event for having sent but not yet having received can be directed to subscription task with request event frame
Transmission is stored in the number for having sent the event in event queue pond (referring to the reference numeral 400 in Fig. 2).
The list specific to task for the event for having sent but not yet having received can be directed to subscription task with request event frame
It sends about being stored in the information that has sent the event in event queue pond.
The list specific to task of subscription event can be sent with request event frame and be had determined to about subscription task
The information of the subscription event of subscription.
The list specific to event of subscription task can be sent with request event frame and be ordered about corresponding with subscription event
Read the information of task.
The all of event queue pond can have been sent with command event frame by deleting by having sent the initialization of event queue
It has sent event queue and has sent event queue pond to initialize.
The addition of event setting and the deletion of event setting (can be referred in Fig. 2 with command event frame to storage device
Reference numeral 30) in store setting data list (referring to the reference numeral 31 in Fig. 2) in addition event setting value or
Person's deletion event setting value from the setting data list.
The addition of event subscription task setting and the deletion of event subscription task setting can be changed with command event frame and closed
The subscription event and the mapping data of subscription task included in the setting data list stored in storage device.
Event system setting can be with the task manager (referring to the reference numeral 200 in Fig. 2) of command event frame weight
The system for building event.
The developer that API library including these API can handle middleware for steel provides efficient processing exploitation and safeguards
Environment.
Fig. 4 is the Event Service frame system in steel processing middleware specifically illustrated according to the embodiment of the present disclosure
The block diagram for the Events Frame that system includes.
With reference to Fig. 4, the Event Service frame in steel processing middleware according to the embodiment of the present disclosure is shown
Task manager 200, event scheduling interface 300 and the specific example for having sent event queue pond 400 that system includes.
Task manager 200 can include event system and access adjuster 210, event setting data management system 220, event
Define manager 230, subscription task-Event mapper 240 and event-subscription task mapper 250.
Event scheduling interface 300 can include interim queue management device 310 of awaiting orders, multiple interim queue accesses adjustment of awaiting orders
Device 311,312 and 313, multiple interim queues 321,322 and 323 of awaiting orders, event transmitter manager 330, multiple events are sent
Device 331,332 and 333 and interim queue selector 340 of awaiting orders.
Multiple event queue managers 410,420 and 430, multiple of having sent can be included by having sent event queue pond 400
Event queue has been sent to access adjuster 411,421 and 431 and multiple sent event queue 412,422 and 432.
In Fig. 4, every group of multiple components are shown as component there are three tools.However, this is the example for description, without
It should be considered for purposes of limitation.For example, the number of component can with the Event Service processing procedure of Events Frame 20 and
Variation.Multiple components in each group can perform identical function, and therefore can be assuming that there are single in each group
It is described in the case of component.
In order to ensure that event defines information and wherein subscription event is mapped to the mapping data of corresponding subscription task
Integrality, when service processor 21 to 2N additions/deletion/search events defines information and mapping data, event system accesses
Adjuster 210 can define information and mapping data with authorization service processor 21 to 2N Access Events.
Event setting data management system 220 can be obtained or be changed to be set about the event of subscription event and subscription task
Value and mapping data.
Event defines manager 230 can be by receiving the event setting value for data management system 220 being set to obtain by event
Information, which is defined, creating event either can create or delete in response to the request of the API from mission application software 10
Event defines information.
Subscription task-Event mapper 240, which can manage wherein task data, has the mapping data of priority.Namely
It says, subscription task-Event mapper 240 can manage mapping data so that can also search for being mapped to the subscription to be searched for times
The subscription event of business.
Event-subscription task mapper 250, which can manage wherein event data, has the mapping data of priority.Namely
It says, event-subscription task mapper 250 can manage mapping data so that can also search for being mapped to the subscription thing to be searched for
The subscription task of part.
Interim queue management device 310 of awaiting orders can create/delete the interim queue 321 of awaiting orders of interim storage event, and
The information of the state about queue 321 of awaiting orders temporarily can be managed.
Interim queue accesses adjuster 311 of awaiting orders can adjust access rights to prevent queue management device 310 of awaiting orders temporarily
Queue 321 of awaiting orders temporarily is accessed simultaneously with event transmitter 331, and is therefore safeguarded and be stored in interim queue 321 of awaiting orders
The integrality of subscription event.
Interim queue 321 of awaiting orders can be created as corresponding to event transmitter 331 and can subscribe to thing with interim storage
Part.Subscription event can be sent to corresponding subscription task by event transmitter 331.
Event transmitter manager 330 can create/and deletion event transmitter 331 and can managing sends about event
The information of the state of device 331.
Interim queue selector 340 of awaiting orders is obtained from queue management device 310 of awaiting orders temporarily about queue 321 of awaiting orders temporarily
The information of state, and by event transmitter 331 be determined as send subscription event event transmitter.Later, service processor
21 to 2N can be stored in subscription event in interim queue 321 of awaiting orders, and then can be with request event transmitter manager
330 perform transmission processing.
Information about the state for having sent event queue 412 can be managed by having sent event queue manager 410.It has sent out
Event queue is sent, which to access adjuster 411, can adjust access rights to prevent from service processor and event transmitter 301 simultaneously
It accesses, and therefore safeguards the integrality for being stored in and having sent the event of the subscription in event queue 412.
The subscription event sent by event scheduling interface 300 can be stored by having sent event queue 412 so that subscribe to event
Until can waiting until that subscription task receives subscription event.
In addition, such subscription event can include the event occurrence of variables message 40 of event id and variable data.
Fig. 5 is the Event Service frame system for showing to handle middleware according to the steel of another embodiment in the present disclosure
Block diagram.
When compared with frame system shown in Fig. 2, frame system shown in fig. 5 further includes to send and receive message
API, intercommunication interface 700, message manager 800 and memory manager 900.
The other structures of frame system can understand from the description of the frame system provided with reference to Fig. 2, therefore will omit
To its repetitive description.
As shown in figure 5, API library 100 can have following A PI, the API to have message sending function and message sink work(
It can so that task can send message to other objects (for example, Events Frame 20) and can receive message from other objects.
Furthermore it is possible to the Event Service in response to the API of mission application software 10 asks to distribute multiple service processors
21 to 2N.Herein, it can send or receive by the API of such as event subscription or establishment etc or by message come into behaviour
Part service request.
In detail, when receiving message to 1N from task 11, service processor 21 to 2N responds message, then
Events Frame 20 can create event and send subscription event.
In addition, event scheduling interface 300 can be by the way that the event of subscription to be converted into message and send the message to order
Task is read to send subscription event.
That is, when task 11 to 1N request events creates, service processor 21 to 2N can make the request
Response, then the event created can be converted into message by Events Frame 20, and can be sent the message to subscription and be appointed
Business.
For this purpose, intercommunication interface 700 is by service processor 21 to 2N, task manager 200, message manager 800 and storage
Device manager 900 is connected to each other so that sending and receiving including message, the establishment of event and subscribes in being sent in of event
Event Service can be handled interactively.In addition, message manager 800 can be controlled according to the instruction of intercommunication interface 700
Message sends and receives.
Memory manager 900 is the component for memory interoperability services provided by Events Frame 20, and will be
It is described referring to Fig. 6.
Fig. 6 is the block diagram for the memory interoperability services for showing frame system processing as shown in Figure 5.
With reference to Fig. 6, it is included in steel for the PLC of unit control and handles component in 1 grade of system, and PLC
Memory can be monitored by mission application software.Mission application software can be asked to run, and this according to Event Service
In the case of, the information of PLC memories can be included in the message, being then transmitted to Events Frame 20 by API library 100.In addition,
The message can include task ID.
Service processor 21 can respond the service request that memorizer information includes.
Since memorizer information is sent to Events Frame 20 in form of a message, intercommunication interface 700 believes memory
Breath is sent to message manager 800 to perform memory interoperability services, and message manager 800 can pass memorizer information
It send to memory manager 900.
Memory manager 900 can store the memorizer information of PLC.If new memorizer information 920 is from message pipe
Reason device 800 be sent to memory manager 900, then memory manager 900 can by new memorizer information 920 with previously
The memorizer information 910 of storage compare to determine if to meet event criteria.If in addition, meeting event criteria, deposit
Reservoir manager 900 can will be delivered to service processor, and can order establishment thing about the information for the event to be created
Part.Hereafter, event can be created by having received the service processor of the information about event.
Fig. 7 is the flow chart for showing memory interoperability services shown in Fig. 6.
First, mission application software can detect the variation (S710) in the memory area of PLC, and can pass through
API library 100 sends service request to Events Frame 20.By the way that the memorizer information about the variation in memory area will be included
Message be sent to Events Frame 20 to carry out service request (S720).Later, service processor responds service request
(S730)。
It is next determined that whether service request is memory intercommunication request (S740), if service request is that memory is mutual
Memorizer information and previously stored memorizer information, then be compared (S750) by logical request.If comparison result is unsatisfactory for
Event criteria then updates storage device information (S754), will be it is determined that for Event Service if comparison result meets event criteria
(S760)。
If it is confirmed as Event Service, event request to create can be carried out to send subscription event (S770), such as
It is not determined to Event Service to fruit, then can perform Message Processing to send message (S780).
Fig. 8 is to show that the processing event in Event Service frame system that is used for according to the embodiment of the present disclosure is created
Build the sequence diagram of the processing of request.The non-limiting example of processing shown in fig. 8.
With reference to Fig. 8, if task requests create event (S510), service processing for the service processor of Event Service
Device can be defined manager transmission event with request event and define information (S531), and can receive and define information request to event
Response (S532).As an alternative, in order to ensure that event defines the data integrity of information, service processor can be in request event
The forward direction event system access adjuster request Access Events for defining information define information (S521), and can obtain to accessing
Event defines the license (S522) of information.
Service processor defines information to create the consistent information for having and being defined with event in information using event
Event.
In addition, service processor request is awaited orders temporarily, queue selector distributes queue (S541) of awaiting orders.Then, it awaits orders temporarily
Queue selector can ask queuing message (S542) of awaiting orders, and can receive to the team that awaits orders to interim queue management device of awaiting orders
The response (S543) of column information request.Interim queue selector of awaiting orders can be obtained from the response to awaiting orders queuing message request
About the status information for queue of awaiting orders temporarily, and it can determine the event transmitter that will send subscription event.Later, it treats temporarily
Life queue selector can reply to service processor and have been allocated for queue (S544) of awaiting orders.
Receive report complete await orders queue assignment reply after, service processor can will ask create event
It is stored in interim queue of awaiting orders as subscription event.Later, service processor can be with request event transmitter manager processes
Subscription event (S561) and can receive subscribe to event handling response (S562).In addition, since service processor and event are sent out
Send device that can access interim queue of awaiting orders simultaneously, therefore, for the data integrity for the queue that ensures to await orders, service processor temporarily
The forward direction that the event created is stored in as subscription event in queue of awaiting orders temporarily can will asked to await orders temporarily queue accesses
Manager request accesses queue (S551) of awaiting orders temporarily, and can obtain the license (S552) to accessing queue of awaiting orders temporarily.
After subscription event handling response is received, service processor can reply to task and create event
(S570)。
In addition, after event handling response is subscribed to, event transmitter manager can perform hair with request event transmitter
Send processing (S580).
Therefore, according to the embodiment of the present disclosure, can store can be in response to primary for Event Service frame system
The event request to create of progress carrys out the subscription event of Batch sending, and can reply the event of having created.Therefore, can subtract
Few task after request event establishment waits for event to create the response stand-by period completed.
Fig. 9 is to show that the processing event in Event Service frame system that is used for according to the embodiment of the present disclosure connects
Receive the sequence diagram of the processing of request.The non-limiting example of processing shown in Fig. 9.
With reference to Fig. 9, if task to the service of service processor request event to receive event (S610), service processor
It can ask to have sent event queue access adjuster inspection subscription event (S621) and subscription event response can be received.Such as
Fruit does not have corresponding subscription event, that is, if event transmitter waits for scheduling request, has sent event queue and has accessed adjuster
Can not there is no subscription event (S622) to subscribing to event inspection request and replying.
As described in reference to fig. 8, if event transmitter manager request event transmitter performs transmission processing (S580),
The subscription event being stored in interim queue of awaiting orders may be used in event transmitter.This can be by replicating about the event of subscription
Information and data perform.In addition, for the data integrity for the queue that ensures to await orders temporarily, service processor can be using ordering
The forward direction queue accesses adjuster request of awaiting orders temporarily for readding event is accessed and is awaited orders queue (S631) temporarily, and can obtain to visiting
Ask the license (S632) of interim queue of awaiting orders.
Next, event transmitter can send event queue to event queue access adjuster request access has been sent
(S641), and it can obtain the license (S642) of event queue has been sent to access.
Later, subscription event can be stored in and send in event queue by event transmitter, and can be by storage
The state of subscription event, which is sent to, has sent event queue access adjuster (S650).
After subscription event is stored in and has sent in event queue, sent event queue access adjuster can be to
Service processor notice subscription event (S660).
If accessing adjuster inspection in addition, service processor request has sent event queue and subscribing to event (S621'),
Service processor (S670) can be replied for certain by having sent event queue access adjuster.
Next, service processor, which can receive event request transmission event, receives reply (S680).That is,
Subscription task can be received by requesting the task of event reception.
Although embodiment in the present disclosure has shown and described above by reference to attached drawing, the scope of the present invention is unlimited
In this, and it will be apparent to those skilled in the art that the sheet that is defined by the appended claims can not departed from
It modifies and changes in the case of the range of invention.
Claims (14)
1. a kind of Event Service method of steel processing middleware, the Event Service method is by mission application software and Events Frame
It performs, the mission application software includes Application Programming Interface (API) library that permission task sends out Event Service request, the thing
Part method of servicing includes：
Service processor responds Event Service request；
Information is defined based on the event for defining event id and size of data to create event；And
If the information about the event created is consistent with the information about requested subscription event, by reference to event
The event created as requested subscription event is sent to and is mapped to requested subscription thing by the mapping data of manager
The subscription task of part.
2. Event Service method according to claim 1, wherein, the establishment of event includes：
If the Event Service request includes memorizer information, memory manager is by the memorizer information with previously depositing
The memorizer information of storage is compared, to determine whether to meet event criteria；And
If meeting the event criteria, the service processor is determined based on the event for defining event id and size of data
Adopted information creates event.
3. Event Service method according to claim 1, wherein, using the event created as requested subscription event
Be sent to the subscription task be by via event scheduling interface send requested subscription event be performed or
Requested subscription event is converted into what is performed after message.
4. Event Service method according to claim 3, wherein, the event scheduling interface includes：
Event transmitter is configured to the subscription event being sent to subscription task corresponding with the subscription event；With
And
The interim queue of awaiting orders accordingly created with the event transmitter, the interim queue of awaiting orders is for described in interim storage
Subscription event.
5. Event Service method according to claim 1, wherein, the task manager includes：
Event defines manager, is configured to create and deletes the event and defines information；
Subscription task-Event mapper, being configured to management wherein task data has the mapping data of priority；And
Event-subscription task mapper, being configured to management wherein event data has the mapping data of priority.
6. a kind of Event Service frame system of steel processing middleware, the Event Service frame system is by least one processor
It realizes and including mission application software and Events Frame, the mission application software sends out Event Service including permission task please
The API library asked, the Events Frame include：
Service processor is configured to respond Event Service request；
Task manager, the event for being configured to management definition event id and size of data define information, and manage wherein
Information about requested subscription event is mapped to the mapping data of corresponding subscription task；And
Event scheduling interface, wherein, if about the event for defining information creating based on the event by the service processor
Information it is consistent with the information about requested subscription event, then the event scheduling interface is using the event created as institute
The subscription event of request is sent to subscription task.
7. Event Service frame system according to claim 6, further includes memory manager, wherein, if the thing
Part service request includes memorizer information, then the memory manager is by the memorizer information and previously stored memory
Information is compared, to determine whether to meet event criteria and order establishment event.
8. Event Service frame system according to claim 6, further include message manager, the message manager by with
It is set to and the subscription event is converted into message described in information and sending.
9. Event Service frame system according to claim 6, wherein, the API library provides API, and task passes through described
API request Event Service, the Event Service include：For creating the event definition, event subscription, event that event defines information
Event establishment, event reception and the event definition for subscribe to cancellation, information being defined based on event are deleted.
10. Event Service frame system according to claim 6, wherein, the task manager includes：
Event defines manager, is configured to create and deletes the event and defines information；
Subscription task-Event mapper, being configured to management wherein task data has the mapping data of priority；And
Event-subscription task mapper, being configured to management wherein event data has the mapping data of priority.
11. Event Service frame system according to claim 6, wherein, the Events Frame further includes the event of transmission
Queue pond, the event queue pond that sent have sent event queue including multiple, have been ordered by what the event scheduling interface was sent
Read event it is described sent wait until that subscription task receives the subscription event in event queue until.
12. Event Service frame system according to claim 11, wherein, the Events Frame further includes Event Service prison
Survey device, the Event Service monitor is configured to monitor the task manager, the event scheduling interface and described has sent out
Event queue pond is sent, the mission application software will be sent to about the information of the state of the subscription event.
13. Event Service frame system according to claim 6, wherein, the event scheduling interface includes：
Event transmitter is configured to the subscription event being sent to subscription task corresponding with the subscription event；With
And
The interim queue of awaiting orders accordingly created with the event transmitter, the interim queue of awaiting orders is for described in interim storage
Subscription event.
14. Event Service frame system according to claim 13, wherein, the event scheduling interface further includes to be treated temporarily
Queue selector is ordered, the interim queue selector of awaiting orders is configured to the event transmitter that selection sends the subscription event.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR20150146725 | 2015-10-21 | ||
| KR10-2015-0146725 | 2015-10-21 | ||
| KR1020160132929A KR101889159B1 (en) | 2015-10-21 | 2016-10-13 | Mthoed and framework system for evnet service of steel process middleware |
| KR10-2016-0132929 | 2016-10-13 | ||
| PCT/KR2016/011586 WO2017069468A1 (en) | 2015-10-21 | 2016-10-14 | Event service method of steel process middleware, and framework system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108140008A true CN108140008A (en) | 2018-06-08 |
| CN108140008B CN108140008B (en) | 2022-08-23 |
Family
ID=58743398
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201680062015.8A Active CN108140008B (en) | 2015-10-21 | 2016-10-14 | Event service method and framework system for steel processing middleware |
Country Status (2)
| Country | Link |
|---|---|
| KR (1) | KR101889159B1 (en) |
| CN (1) | CN108140008B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR102509402B1 (en) * | 2020-12-09 | 2023-03-13 | 주식회사 에이앤에이 | A method for processing the event on the platform |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6549956B1 (en) * | 1998-11-30 | 2003-04-15 | Hewlett Packard Company | Mechanism for connecting disparate publication and subscribe domains via the internet |
| US20070011266A1 (en) * | 2005-07-05 | 2007-01-11 | Microsoft Corporation | Automatic create, update and delete event publishing |
| US20070067409A1 (en) * | 2005-08-26 | 2007-03-22 | At&T Corp. | System and method for event driven publish-subscribe communications |
| KR20100076840A (en) * | 2008-12-26 | 2010-07-06 | 주식회사 포스코 | Middleware for controling steel process and method for providing service in the middleware |
| US20120110077A1 (en) * | 2010-07-30 | 2012-05-03 | The Mcgraw-Hill Companies, Inc. | System and Method Using A Simplified XML Format for Real-Time Content Publication |
| US20130067024A1 (en) * | 2011-09-12 | 2013-03-14 | Microsoft Corporation | Distributing multi-source push notifications to multiple targets |
| CN103927218A (en) * | 2014-04-30 | 2014-07-16 | 广州唯品会网络技术有限公司 | Event dispatching method and system |
| CN103944924A (en) * | 2014-05-15 | 2014-07-23 | 重庆邮电大学 | Ubiquitous network publish-subscribe middleware model based on RESTful |
| WO2014171130A1 (en) * | 2013-04-17 | 2014-10-23 | 日本電気株式会社 | Information processing system, deployment method, processing device, and deployment device |
| CN104618432A (en) * | 2014-12-30 | 2015-05-13 | 北京红马传媒文化发展有限公司 | Event sending and receiving handling method and system |
| US20150142501A1 (en) * | 2013-11-18 | 2015-05-21 | Nuwafin Holdings Ltd | System and method for executing business services and enhancing business performance through a business process modeling notation |
-
2016
- 2016-10-13 KR KR1020160132929A patent/KR101889159B1/en active IP Right Grant
- 2016-10-14 CN CN201680062015.8A patent/CN108140008B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6549956B1 (en) * | 1998-11-30 | 2003-04-15 | Hewlett Packard Company | Mechanism for connecting disparate publication and subscribe domains via the internet |
| US20070011266A1 (en) * | 2005-07-05 | 2007-01-11 | Microsoft Corporation | Automatic create, update and delete event publishing |
| US20070067409A1 (en) * | 2005-08-26 | 2007-03-22 | At&T Corp. | System and method for event driven publish-subscribe communications |
| KR20100076840A (en) * | 2008-12-26 | 2010-07-06 | 주식회사 포스코 | Middleware for controling steel process and method for providing service in the middleware |
| US20120110077A1 (en) * | 2010-07-30 | 2012-05-03 | The Mcgraw-Hill Companies, Inc. | System and Method Using A Simplified XML Format for Real-Time Content Publication |
| US20130067024A1 (en) * | 2011-09-12 | 2013-03-14 | Microsoft Corporation | Distributing multi-source push notifications to multiple targets |
| WO2014171130A1 (en) * | 2013-04-17 | 2014-10-23 | 日本電気株式会社 | Information processing system, deployment method, processing device, and deployment device |
| US20150142501A1 (en) * | 2013-11-18 | 2015-05-21 | Nuwafin Holdings Ltd | System and method for executing business services and enhancing business performance through a business process modeling notation |
| CN103927218A (en) * | 2014-04-30 | 2014-07-16 | 广州唯品会网络技术有限公司 | Event dispatching method and system |
| CN103944924A (en) * | 2014-05-15 | 2014-07-23 | 重庆邮电大学 | Ubiquitous network publish-subscribe middleware model based on RESTful |
| CN104618432A (en) * | 2014-12-30 | 2015-05-13 | 北京红马传媒文化发展有限公司 | Event sending and receiving handling method and system |
Non-Patent Citations (3)
| Title |
|---|
| 廖小平等: "基于XML和发布/订阅机制的主动服务系统", 《计算机应用与软件》 * |
| 潘国伟等: "消息中间件在电力调度自动化系统中的应用", 《电气应用》 * |
| 王稳军等: "可扩展发布/订阅中间件技术研究", 《指挥信息系统与技术》 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108140008B (en) | 2022-08-23 |
| KR20170047169A (en) | 2017-05-04 |
| KR101889159B1 (en) | 2018-08-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11200540B2 (en) | Fabrication, distribution, and integrated order processing system | |
| US9959337B2 (en) | Independent data processing environments within a big data cluster system | |
| Leng et al. | Blockchained smart contract pyramid-driven multi-agent autonomous process control for resilient individualised manufacturing towards Industry 5.0 | |
| Dominic et al. | Efficient dispatching rules for dynamic job shop scheduling | |
| WO2018005643A1 (en) | Robot fleet dispatch request system | |
| US8230424B2 (en) | General interface with arbitrary job managers | |
| US20200151008A1 (en) | Project Scheduling in a Heterogeneous Distributed Computing Environment | |
| US20040044718A1 (en) | Submitting jobs in a distributed computing environment | |
| US20110010134A1 (en) | Active building information modeling apparatus and method | |
| Akbari Torkestani | A new approach to the job scheduling problem in computational grids | |
| JP6414185B2 (en) | Information processing apparatus, resource allocation system, and resource allocation method | |
| US10080233B2 (en) | Method for providing M2M data | |
| Álvarez-Gil et al. | A discrete firefly algorithm for solving the flexible job-shop scheduling problem in a make-to-order manufacturing system | |
| Chawla et al. | Effect of nature-inspired algorithms and hybrid dispatching rules on the performance of automatic guided vehicles in the flexible manufacturing system | |
| US20160026735A1 (en) | Method and system for managing data in a manufacturing execution system | |
| Wang et al. | Distributed feedback control algorithm in an auction-based manufacturing planning and control system | |
| CN108140008A (en) | Steel handles the Event Service method and frame system of middleware | |
| US10489803B2 (en) | Systems and methods of enabling forecasting | |
| Alexakos et al. | Exposing MES functionalities as enabler for cloud manufacturing | |
| Vieira et al. | A knowledge based system for supporting sustainable industrial management in a clothes manufacturing company based on a data fusion model | |
| US20200019385A1 (en) | Application development environment providing system, application development environment provision method, and terminal device | |
| US20220058727A1 (en) | Job based bidding | |
| RU2660299C2 (en) | Earth remote sensing data photogrammetric processing adaptive distributed system | |
| JP2021117945A (en) | Method and system for customizing work order | |
| US11562265B2 (en) | Intelligent data analytics |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address | ||
| CP03 | Change of name, title or address |
Address after: Seoul City, Korea Patentee after: POSCO Holdings Co.,Ltd. Address before: Gyeongbuk, South Korea Patentee before: Style Society POSCO |
|
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230612 Address after: Gyeongbuk, South Korea Patentee after: POSCO Co.,Ltd. Address before: Seoul City, Korea Patentee before: POSCO Holdings Co.,Ltd. |