CN1326361C - Method for implementing communication of information among multiple platforms - Google Patents
Method for implementing communication of information among multiple platforms Download PDFInfo
- Publication number
- CN1326361C CN1326361C CNB2005100237747A CN200510023774A CN1326361C CN 1326361 C CN1326361 C CN 1326361C CN B2005100237747 A CNB2005100237747 A CN B2005100237747A CN 200510023774 A CN200510023774 A CN 200510023774A CN 1326361 C CN1326361 C CN 1326361C
- Authority
- CN
- China
- Prior art keywords
- assembly
- rule
- component
- flow
- treatment system
- 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.)
- Expired - Fee Related
Links
Images
Landscapes
- Computer And Data Communications (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The present invention relates to a method for realizing information communication among multiple platforms, which is realized by the following procedures: (1) automatically discovering a rule / flow system component, M other system components and N standard components by a central drive processing system; (2) loading and initializing the rule / flow system component so as to generate a rule/ flow base; (3) loading and initializing the M other system components and the N standard components; (4) respectively sending registration event messages to the rule / flow system component by the M other system components and the N standard components; (5) serializing the messages by the rule / flow system component and adding in an event base; (6) sending a service request to the central drive processing system by two or more than two components of the M other system components and the N standard components, and processing the central drive processing system according to the event base and the rule / flow base; (7) feeding back required information towards requesters for service by the rule / flow system component.
Description
Technical field
The present invention relates to a kind of method of information interchange, relate in particular to a kind of note interchange assembly, multimedia message interchange assembly, call voice interchange assembly, email exchange assembly, the Internet realized and exchange the method for communication of information among multiple platforms such as assembly in real time.
Background technology
Along with the continuous development of society, the affairs that the modern will face every day are more and more.Work hours on daytime, more people is in a kind of state of running around here and there; Evening, owing to work reason or overtime work or be swamped with.
In this case, government, group, enterprise and all kinds of tissue will effectively organize subordinate's member aggregating to carry out interchange together, the discussion affairs are more and more difficult; A lot of important affairs also because can't gather the member discusses, decides by vote and slowly can't determine, have delayed the time, have reduced efficient.
The leader of government, group, enterprise and each histioid director recognize that gradually original office mode can't adapt to fast-developing needs of society, and the cry of innovation is more and more higher.
At present, realize that the method for identical platform information interchange has a lot, local is arranged, wireless, trans-regional or the like; How solving the method that relates to the different platform information interchange is the problem of pendulum in face of the science and technology personnel.
Summary of the invention
The technical issues that need to address of the present invention have provided a kind of method that realizes communication of information among multiple platforms, are intended to address the above problem.
In order to solve the problems of the technologies described above, the present invention realizes by following steps:
Automatically find all component by the center driven treatment system: comprise rule/flow system assembly, M other system component and N standard package; Described M, N are positive integers;
Load and initialization rule/flow system assembly, and create-rule/flow process storehouse;
Load and initialization M other system component and N standard package;
M other system component and N standard package are sent registered events message to rule/flow system assembly respectively;
Rule/flow system assembly adds event base after with message sequence;
The assembly more than two or two in M other system component and N standard package is after center driven treatment system transmission service request, and described center driven treatment system can be handled according to event base and rule/flow process storehouse;
By rule/flow system assembly to service requester feedback information needed;
Compared with prior art, the invention has the beneficial effects as follows: can realize cross-platform interaction fully between each intercommunion platform; No matter use user that the user of SMS also is to use phone also or use the user of computer network to realize interaction each other, improved operating efficiency.
Description of drawings
Fig. 1 is a flow chart of the present invention;
Fig. 2 is each standard package register flow path figure;
Fig. 3 is each standard package state exchange flow chart;
Embodiment
Below in conjunction with accompanying drawing and embodiment the present invention is described in further detail:
By Fig. 1, Fig. 2 as seen: find all component automatically: comprise rule/flow system assembly, M other system component and N standard package by the center driven treatment system; Described M, N are positive integers 1; System component is a kind of special condition code that has; Have special life cycle, system component started automatically after core started during operation, and system component was closed automatically when core was closed during operation, and core must restart when system component upgraded the back operation;
Load and initialization rule/flow system assembly, and create-rule/flow process storehouse 2;
Load and initialization M other system component and N standard package 3;
M other system component and N standard package are sent registered events message 4 to rule/flow system assembly respectively; Described registered events message is made up of two parts, and a part is an Event Description; Another part is executing rule or flow process; For example---" if standard package is unusual, just write abnormal log earlier, report an error again." this incident is after registration, rule/flow system assembly writes " standard package is unusual " to event base earlier, writes " write abnormal log, report an error " to rule/flow process storehouse again;
Rule/flow system assembly adds event base 5 after with message sequence;
The assembly more than two or two in M other system component and N standard package is after center driven treatment system transmission service request, and described center driven treatment system can handle 6 according to event base and rule/flow process storehouse;
By rule/flow system assembly to service requester feedback information needed 7; Described feedback information needed: if standard package is unusual, the center driven treatment system hands over rule/flow system assembly to mate anomalous event, rule/flow system assembly searched events storehouse, find " standard package is unusual " incident, matched rule/flow process in rule/flow process storehouse---" write abnormal log, report an error " then, this message is returned the center driven treatment system, call corresponding assembly by the center driven treatment system and finish " write abnormal log, report an error "; Because registered one group of service interface object that the service object is relevant with a group to the center driven treatment system when assembly starts, so the center driven treatment system can know that calling which assembly comes processing rule/flow process;
Described rule/flow system assembly, M other system component have different condition code 8 respectively with N standard package;
As seen from Figure 3: a described N standard package can be one of following state: load---assembly is by the state after successfully installing; Ready---assembly initialization finishes, and can enter the state of starting or stoping; Starting---assembly enters starting state, starts attribute and is activated; Stopping---assembly is out of service; Activating---assembly starts successfully, enters operational mode; Unloading---assembly is excluded from system; And M other system component just starts after central authorities drive the treatment system startup automatically, enter state of activation, in servicely can not be stopped, unload, upgrade the back system and must restart, unloading must could unload by configuration file after the center driven treatment system stops; Between all activated assembly, can both ask service between activation component and the center driven treatment system, be requested assembly or the center driven treatment system all can be carried out service request 9;
And can carry out priority to the service request of all component and consider 10;
Described each assembly or center driven treatment system are when other assembly or center driven treatment system are sent service request, this assembly or the center driven treatment system that can carry out service request can realize operation by following state: wait---indicate modulated degree job run, but its off-duty still; Moving---the indication operation moves; Just in dormancy---the indication operation is because sleep request or dispatch it and just move after through certain delay and just in dormancy; Do not have---the indication operation is not in wait, operation or dormancy; But when having created operation not dispatched it as yet, operation will be in this state; After operation is finished operation or has been cancelled, it also will be in this state 11;
In the step 10: described priority consider to define following one of them: moment operation---operation has precedence over other operation usually; They should be the operations of short time operation or less use processor, and therefore, they can not hinder other job run moment; Short operation---operation can be finished in a second usually, but also may the time a little long a little; They are at running background, and have precedence over the All Jobs except the moment operation; Long operation---the background job of longer time operation is represented in operation; They are just operation after moment operation and short operation have moved only; Making up operation---the operation that is associated with the structure task is represented in operation; They are lower than the priority of long operation.Make up only just operation after all long operations are finished of operation; Operation---the priority of operation in system is minimum in modification; But those tasks of providing the information user that can help the replenish user interface can not wait for usually are provided for they; And the default priorities of definition operation is long operation;
In the step 6,7: when needs were visited and handled same object, described object was awarded the agreement to the exclusive reference of shared object;
Core (being called the center driven treatment system again) when main feature of the present invention is embodied in based on a small efficiently operation, expand various plug-in units flexibly, be combined into various systems longitudinally, and be aided with rule/flow engine and other system component, the various application of horizontal composition.
When native system starts, core operation earlier during operation, core is found all component automatically when moving subsequently, and loading system assembly at first; When all system component loads and after initialization finishes, system loads and initialization standard package; When all component loads and after initialization finished, vertical combination of system was finished; Any assembly can be to other component passes message, and for example standard package G can send registered events message to rule/flow system assembly, and rule/flow system assembly adds event base after with message sequence; The rest may be inferred, and system promptly finishes horizontal combination.Initialization of the present invention this moment is finished, any assembly (for example assembly G) can send service request, after corresponding assembly (for example rule/flow system assembly) is received service request, can handle and generate the service feedback information and reply to the requestor according to corresponding configuration (for example event base and rule/flow process storehouse) by corresponding assembly (for example rule/flow system assembly).
Each assembly among the present invention all is the component object of a standard, the life cycle that they can manage them by an administration agent; Each assembly all has a condition code to represent its identity.This condition code is unique in system, in case condition code is assigned to certain assembly, other assembly just can not use, unless this assembly is reinstalled.Condition code comprises when assembly upgrades in case distribution just can not be changed.
Each assembly all must be one of following state:
● loading---assembly is by the state after successfully installing;
● ready---assembly initialization finishes, and can enter the state of starting or stoping;
● starting---assembly enters starting state, starts attribute and is activated;
● stopping---assembly is out of service;
● activating---assembly starts successfully, enters operational mode;
● unloading---assembly is excluded from system.
After at first core starts when operation, the assembly that the automatic discovery of its meeting will be loaded, and handle component is set as loading condition; Successfully just change ready state automatically over to if assembly loads, if having unusually, core just triggers anomalous event during operation, and handle component changes unloaded state over to; If having unusual is system component, core just triggers anomalous event during operation, and writing daily record unusually, core withdraws from unusually during operation; Ready assembly can make it enter unloaded state, upgrade and reload later on or starting state (after the system component renewal, core must restart during operation) by Event triggered at any time; Core can activate it automatically during assembly operating after the startup; The assembly that activates can make it stop (system component can not be stopped) by Event triggered; Core is set to ready state to it automatically during assembly operating after stopping.
Core kept communicating by letter when assembly passed through the assembly context object with operation; The assembly context object by when operation core when assembly starts, create.Can not the transmitting assembly context object between the assembly, they are privately owned.After assembly stops, the assembly context object can not be accessed, if attempt to visit a context object that is stopped assembly, core will be dished out unusually during operation.
Each assembly all can provide one group of co-operating service, and the developer of an assembly provides one group of service interface object that the service object is relevant with a group.The service object of assembly core registration oneself when operation will have a service registry object after the registration, each service registry object all comprises one or more service objects.Core allows the dynamic registration and unregistration service object of assembly during operation, each registration service object, and core all will be made corresponding License Check during operation, to guarantee service object's legitimacy.
Can call the service object who has registered by the context object of assembly, and obtain service by the service object.
Can service be configured by service object's configuration attribute.
Incident of the present invention mainly is divided three classes:
● Service events---report service object's incidents such as registration, unloading and attribute change;
● assembly incident---incidents such as reporting component state change;
● core event---the state of report core, abnormality warnings, incident such as make mistakes.
The present invention finds incident by a listening components, by log component (or other self-defined assembly) recording events.
When assembly sends service request, the assembly that accepts request can be carried out service request, at this moment will produce a group job, this group job be exactly one group can asynchronous execution the working cell.
When carrying out service, assembly will be created operation, dispatch it then.In case dispatched operation, the job queue of hard core control in the time of it will being added into by operation.Core uses the backstage scheduling thread to manage all pending operations during operation.When the operation of operation is finished, will from formation, remove it, which operation will be core will determine next to move during operation.When operation became active state, core will be called operation method to it during operation.
If dispatched an operation, decision no longer needs it again then, then can use the method for abandoning to stop this operation.If cancellation during operation this operation do not bring into operation as yet, then can abandon immediately and can bootup window.On the other hand, if operation brings into operation, then will decide it whether to want echo canceling by operation.When attempting the cancellation operation, use method of attachment to wait for the cancellation operation.Than the light slightly method of cancellation operational degree is the sleep method.For the method, if operation does not bring into operation as yet, then the method will cause this operation to be hung up by indefinite duration.Core will still be remembered this operation during operation, and awakening method calls and will this operation be added into waiting list, finally still will carry out this operation.
Operation will be experienced several states in its life cycle.Not only can be by waiting and handle it such as abandoning method and sleep method, and in the platform operation with when finishing this operation, its state also can be changed.Operation can be experienced following state:
● wait for---indicate modulated degree job run, but its off-duty still.
● moving---the indication operation moves.
● just in dormancy---the indication operation is because sleep request or dispatch it and just move after through certain delay and just in dormancy.
● do not have---the indication operation is not in wait, operation or dormancy.But when having created operation not dispatched it as yet, operation will be in this state.After operation is finished operation or has been cancelled, it also will be in this state.
If the current wait state that is in of operation then can only place resting state with it.The operation that just wakes up in dormancy will make it come back to wait state.To make it turn back to stateless during the cancellation operation.
Job priority can be used for determining the importance of an operation with respect to other operation in the system.The priority that operation is set will not influence the operation in operation, but it can influence the operation the waited for dispatching sequence with respect to other operation.The priority of operation can be one of them of predefined several priority constants:
● moment operation---operation has precedence over other operation usually.They should be the operations of short time operation or less use processor, and therefore, they can not hinder other job run moment.
● short operation---operation can be finished in a second usually, but also may the time a little long a little.They are at running background, and have precedence over the All Jobs except the moment operation.
● long operation---the background job of longer time operation is represented in operation.They are just operation after moment operation and short operation have moved only.
● making up operation---the operation that is associated with the structure task is represented in operation.They are lower than the priority of long operation.Make up only just operation after all long operations are finished of operation.
● operation---the priority of operation in system is minimum in modification.But those tasks of providing the information user that can help the replenish user interface can not wait for usually are provided for they.
The default priorities of operation is long operation.
Can when schedule job, specify dispatch delay.Before schedule job, operation will postpone the millisecond number of appointment.Scheduling wait for or the operation of dormancy without any effect.But scheduling reschedules it after the operation of operation will cause finishing this operation.If operation is repeatedly rescheduled when operation, then it will only reschedule once according to the delay that provides recently.
A plurality of operations among the present invention might need visit and handle same object.The present invention's definition is used to authorize the agreement to the exclusive reference of shared object.When operation need be visited shared object, it can obtain the locking to this object.When it handled this object, it will discharge this locking.
Suppose " operation A " acquisition " locking A ", attempt obtaining " locking B " subsequently.Simultaneously, " locking B " quilt " operation B " hung up, and " operation B " got clogged now, and it waits for " locking A ".This situation is deadlock, is illustrated in to have the bottom-layer design problem when using locking between the operation.Core will help to find deadlock during operation.When the operation manager detected deadlock situation, it will be presented at diagnostic message in the daily record, and can describe deadlock situation.Then, it removes deadlock by the following method: the access right of the locking that will have the operation that gets clogged is authorized to other operation of waiting for these lockings temporarily.
Rule/flow system assembly is an important system assembly of finishing horizontal combination in the native system.Owing to itself be exactly assembly, as long as so its implementation meet above-mentioned component object definition, can select different instruments self-defined with system requirements.
Incident and rule/flow process storehouse selects for use the XML standard to be described, and the user can be self-defined as required.The user can work out self-defining XML resolution component and be articulated on when operation product platform, comes parsing incident and rule/flow process storehouse.
After standard package A transmission event registration information was to rule/flow system assembly, rule/flow system assembly was registered the incoming event storehouse with event information.When Event triggered, rule/flow system assembly mates according to the information in event base and rule/flow process storehouse, and matching result is returned to standard package A.
So just can change the logical relation between the assembly at any time by Configuration events and rule/flow process storehouse, thus the purpose that reaches flexible configuration, freely expands.
Claims (7)
1. a method that realizes communication of information among multiple platforms realizes by following steps: find all component automatically by the center driven treatment system: comprise rule/flow system assembly, M other system component and N standard package; Described M, N are positive integer (1);
Load and initialization rule/flow system assembly, and create-rule/flow process storehouse (2);
Load and individual other system component of initialization M and N standard package (3);
M other system component and N standard package are sent registered events message (4) to rule/flow system assembly respectively; Described registered events message is made up of two parts, and a part is an Event Description; Another part is executing rule or flow process;
Rule/flow system assembly adds event base (5) after with message sequence;
The assembly more than two or two in M other system component and N standard package is after center driven treatment system transmission service request, and described center driven treatment system can be handled (6) according to event base and rule/flow process storehouse;
By rule/flow system assembly to service requester feedback information needed (7).
2. the method for realization communication of information among multiple platforms according to claim 1 is characterized in that: described rule/flow system assembly, M other system component have different condition code (8) respectively with N standard package.
3. the method for realization communication of information among multiple platforms according to claim 2 is characterized in that: a described N standard package can be one of following state: load---assembly is by the state after successfully installing; Ready---assembly initialization finishes, and can enter the state of starting or stoping; Starting---assembly enters starting state, starts attribute and is activated; Stopping---assembly is out of service; Activating---assembly starts successfully, enters operational mode; Unloading---assembly is excluded from system; And system component starts the back and just starts automatically when central authorities drive treatment system, enters state of activation, in servicely can not be stopped, unload, and system must restart after upgrading, and unloading must could unload by configuration file after the center driven treatment system stops; Between all activated assembly, can both ask service between activation component and the center driven treatment system, be requested assembly or center driven treatment system and all can carry out service request (9).
4. the method for realization communication of information among multiple platforms according to claim 3 is characterized in that: and can carry out priority to the service request of all component and consider (10).
5. the method for realization communication of information among multiple platforms according to claim 3, it is characterized in that: described each assembly or center driven treatment system are when other assembly or center driven treatment system are sent service request, this assembly or the center driven treatment system that can carry out service request can realize operation by following state: wait---indicate modulated degree job run, but its off-duty still; Moving---the indication operation moves; Just in dormancy---the indication operation is because sleep request or dispatch it and just move after through certain delay and just in dormancy; Do not have---the indication operation is not in wait, operation or dormancy; But when having created operation not dispatched it as yet, operation will be in this state; After operation is finished operation or has been cancelled, it also will be in this state (11).
6. the method for realization communication of information among multiple platforms according to claim 4 is characterized in that: in the step (10): described priority consider to define following one of them: moment operation---operation has precedence over other operation usually; Short operation---operation can be finished in a second usually, but also may the time a little long a little; Long operation---the background job of longer time operation is represented in operation; Making up operation---the operation that is associated with the structure task is represented in operation; Operation---the priority of operation in system is minimum in modification; And the default priorities of definition operation is long operation.
7. according to the method for the described realization communication of information among multiple platforms of each claim of claim 1 to 6, it is characterized in that: in the step (6,7): when needs were visited and handled same object, described object was awarded the agreement to the exclusive reference of shared object.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100237747A CN1326361C (en) | 2005-02-02 | 2005-02-02 | Method for implementing communication of information among multiple platforms |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100237747A CN1326361C (en) | 2005-02-02 | 2005-02-02 | Method for implementing communication of information among multiple platforms |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1697391A CN1697391A (en) | 2005-11-16 |
| CN1326361C true CN1326361C (en) | 2007-07-11 |
Family
ID=35349929
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100237747A Expired - Fee Related CN1326361C (en) | 2005-02-02 | 2005-02-02 | Method for implementing communication of information among multiple platforms |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1326361C (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2003040887A2 (en) * | 2001-11-08 | 2003-05-15 | International Business Machines Coporation | Automated information technology management system |
| WO2003048934A2 (en) * | 2001-11-30 | 2003-06-12 | Oracle International Corporation | Real composite objects for providing high availability of resources on networked systems |
| US6683851B1 (en) * | 2000-01-05 | 2004-01-27 | Qualcomm, Incorporated | Flow control of multiple entities sharing a common data link |
| CN1532746A (en) * | 2003-03-25 | 2004-09-29 | 富士施乐株式会社 | Information processor and method for safetyly realizing coprocessing |
-
2005
- 2005-02-02 CN CNB2005100237747A patent/CN1326361C/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6683851B1 (en) * | 2000-01-05 | 2004-01-27 | Qualcomm, Incorporated | Flow control of multiple entities sharing a common data link |
| WO2003040887A2 (en) * | 2001-11-08 | 2003-05-15 | International Business Machines Coporation | Automated information technology management system |
| WO2003048934A2 (en) * | 2001-11-30 | 2003-06-12 | Oracle International Corporation | Real composite objects for providing high availability of resources on networked systems |
| CN1532746A (en) * | 2003-03-25 | 2004-09-29 | 富士施乐株式会社 | Information processor and method for safetyly realizing coprocessing |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1697391A (en) | 2005-11-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101178787A (en) | Information communication method used for community old cadres health supervision | |
| US7810098B2 (en) | Allocating resources across multiple nodes in a hierarchical data processing system according to a decentralized policy | |
| US6789101B2 (en) | Automation system uses resource manager and resource agents to automatically start and stop programs in a computer network | |
| GB2483737A (en) | Workflow scheduler for server cluster with blocking assignment of order sensitive flows and non blocking assignment of other flows | |
| CN108563502A (en) | A kind of method for scheduling task and device | |
| CN112667383B (en) | Task execution and scheduling method, system, device, computing equipment and medium | |
| US20100223371A1 (en) | Method for interacting with user and terminal thereof | |
| US20100122263A1 (en) | Method and device for managing the use of a processor by several applications, corresponding computer program and storage means | |
| US8793325B2 (en) | Time and event controlled message processing | |
| CN112230987A (en) | System and method for realizing distributed modular plug-in framework | |
| CN115421898A (en) | Big data task scheduling management system and method based on quartz framework | |
| CN111240819A (en) | Dispatching task issuing system and method | |
| CN111930492B (en) | Task flow scheduling method and system based on decoupling task data model | |
| US9792419B2 (en) | Starvationless kernel-aware distributed scheduling of software licenses | |
| CN116866427B (en) | Unified pushing method and system for heterogeneous messages | |
| CN113821322A (en) | Loosely-coupled distributed workflow coordination system and method | |
| US8458716B2 (en) | Enterprise resource planning with asynchronous notifications of background processing events | |
| CN117251269A (en) | Jenkins resource management method, device, equipment and storage medium | |
| CN111124651B (en) | Method for concurrently scheduling multiple threads in distributed environment | |
| CN1326361C (en) | Method for implementing communication of information among multiple platforms | |
| US20040025007A1 (en) | Restricting access to a method in a component | |
| US20030204551A1 (en) | System and method for providing media processing services | |
| CN101371235B (en) | Device management scheduling method and apparatus thereof | |
| CN115811549B (en) | Cloud edge resource management scheduling method and system supporting hybrid heterogeneous operation | |
| CN113641480B (en) | Task scheduling system and method based on Kubernetes cluster group |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C17 | Cessation of patent right | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20070711 Termination date: 20100202 |