CN101178787A - Information communication method used for community old cadres health supervision - Google Patents
Information communication method used for community old cadres health supervision Download PDFInfo
- Publication number
- CN101178787A CN101178787A CNA2006101182445A CN200610118244A CN101178787A CN 101178787 A CN101178787 A CN 101178787A CN A2006101182445 A CNA2006101182445 A CN A2006101182445A CN 200610118244 A CN200610118244 A CN 200610118244A CN 101178787 A CN101178787 A CN 101178787A
- Authority
- CN
- China
- Prior art keywords
- assembly
- rule
- groupware
- flow
- component
- 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.)
- Pending
Links
Images
Abstract
The invention relates to an information communicating method used for the health care management of veteran cadres in a community, and is realized through the following steps: a rule/flow system groupware, M other system groupware and N standard groupware are automatically found through a central drive processing system (1); the rule/flow system groupware is loaded and initialized and a rule/flow storehouse is generated (2); the M other system groupware and the N standard groupware are loaded and initialized (3); registering affair information is sent respectively from the M other system groupware and the N standard groupware to the rule/flow system groupware (4); the rule/flow system groupware is added into an affair storehouse after the rule/flow system groupware serializes the information (5); when two or more than two groupware in the M other system groupware and the N standard groupware send service requirement to the central drive processing system, the central drive processing system carries out process according to the affair storehouse and the rule/flow storehouse (6); the needed information is fed back to a service applicant through the rule/flow system groupware (7).
Description
Technical field
The present invention relates to a kind of information communication platform, relate in particular to a kind of information communication method that is used for the veteran cadre of community health care management.
Background technology
Along with the continuous development of society, the continuous variation of city management system reform and retired veteran cadre's aging, the status and the effect of the veteran cadre of community work are more and more important.
What emphasize in the modern medical service system is the personalized medicine health care, thinks that everyone is unique individuality, respect the individual character of health care object, especially retired veteran cadre, special experience of life is all arranged, and the war environment in past is abominable, poor life quality, veteran cadre fights north and south for many fronts, heavier to each system damage of health, most veteran cadres suffer from several conditions, and spirit is in case catch a packet, cause harmful effect for veteran cadre's physiology, psychology, be unfavorable for the rehabilitation of body and mind.Health care should be carried out personalized service according to different veteran cadres' different demands.At the psychology of veteran cadre to disease fear, anxiety, the guiding old man adopts a correct attitude towards the disease of oneself, the patient and painstaking explanation state of an illness, be particular about strategy, attention method is held size, avoid the old man is caused spiritual stimulation, encourage the old man to face disease, emphasize the importance of early treatment.
Therefore need improve veteran cadre's individual-data, such as physical data, kinsfolk's situation, special hobby, diet habit, sleep state or the like, the complete written record state of an illness, all write ups go out to be admitted to hospital at every turn, and, formulate the individual and rescue prediction scheme at contingent anxious danger illness; At annual health check-up situation, concrete analysis, dynamic monitoring.According to these information, can well link up, exchange with veteran cadre; Disposition, hobby according to veteran cadre satisfy its demand as far as possible, and veteran cadre has a kind of cordiality, pleasantly surprised sense, can with very actively, the attitude of trusting cooperate our health care.
Therefore a method that is used for information interchange need be in time proposed and the scheme system that solves will be solved and improve targetedly.How designing a kind of information communication method that is used for the veteran cadre of community health care management 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 information communication method that is used for the veteran cadre of community health care management, 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:
Be used to provide to different information communication interaction platform interface service layers by one visit information is gathered;
By a received communication layer that is used to finish different information interaction means the content of different information interactions is classified;
Finish by one the protocol layer of the mutual conversion of data in different formats and agreement internal format data is changed;
The link layer that is sent to different information destinations by the information with the separate sources that receives distributes;
Sending communication layers by one sends data;
Wherein: protocol layer conversion is to carry out to the distortion of another format conversion main body from a form by the message of preserving all form information agents and with message.
Compared with prior art, the invention has the beneficial effects as follows: veteran cadre's personal information is gathered the employing platform management, and the mode that the individual uses is used emergent constantly can calling at any time conveniently; Both used traditional information interaction means, also can in different information interaction means, use.
Description of drawings
Fig. 1, Fig. 2, Fig. 3 are process flow diagrams of the present invention;
Embodiment
Below in conjunction with accompanying drawing and embodiment the present invention is described in further detail: as seen: find all component automatically: comprise rule/flow system assembly, M other system component and N standard package by the center driven disposal system by Fig. 1, Fig. 2, Fig. 3; Described M, N are positive integers 1; 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 disposal system transmission services request, and described center driven disposal 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 disposal 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 disposal system, call corresponding assembly by the center driven disposal 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 disposal system when assembly starts, so the center driven disposal system can know that calling which assembly comes processing rule/flow process;
Described each assembly or center driven disposal system are when other assembly or center driven disposal system are sent services request, can realize by following state in the time of can carrying out this group job of services request: 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 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 disposal system again) when principal 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 services request, after corresponding assembly (for example rule/flow system assembly) is received services request, can according to corresponding configuration (for example event base and rule/flow process storehouse) handle and generate the service feedback information and, reply to the requestor 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 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 services request, the assembly that accepts request can be carried out services request, and this is to 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 waiting status that is in of operation then can only place dormant state with it.The operation that just wakes up in dormancy will make it come back to waiting status.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 (2)
1. an information communication method that is used for the veteran cadre of community health care management realizes by following steps: find all component automatically by the center driven disposal 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 disposal system transmission services request, and described center driven disposal 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. a kind of information communication method that is used for the veteran cadre of community health care management according to claim 1, it 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 disposal 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 disposal system stops; Between all activated assembly, can both ask service between activation component and the center driven disposal system, be requested assembly or center driven disposal system and all can carry out services request (9).
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101182445A CN101178787A (en) | 2006-11-10 | 2006-11-10 | Information communication method used for community old cadres health supervision |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNA2006101182445A CN101178787A (en) | 2006-11-10 | 2006-11-10 | Information communication method used for community old cadres health supervision |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN101178787A true CN101178787A (en) | 2008-05-14 |
Family
ID=39405030
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNA2006101182445A Pending CN101178787A (en) | 2006-11-10 | 2006-11-10 | Information communication method used for community old cadres health supervision |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101178787A (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9442737B2 (en) | 2012-06-15 | 2016-09-13 | International Business Machines Corporation | Restricting processing within a processor to facilitate transaction completion |
| US9448796B2 (en) | 2012-06-15 | 2016-09-20 | International Business Machines Corporation | Restricted instructions in transactional execution |
| US9477514B2 (en) | 2012-06-15 | 2016-10-25 | International Business Machines Corporation | Transaction begin/end instructions |
| US9529598B2 (en) | 2012-06-15 | 2016-12-27 | International Business Machines Corporation | Transaction abort instruction |
| CN104364778B (en) * | 2012-06-15 | 2017-02-08 | 国际商业机器公司 | Saving/restoring selected registers in transactional processing |
| US9740549B2 (en) | 2012-06-15 | 2017-08-22 | International Business Machines Corporation | Facilitating transaction completion subsequent to repeated aborts of the transaction |
| US9740521B2 (en) | 2012-06-15 | 2017-08-22 | International Business Machines Corporation | Constrained transaction execution |
| US9766925B2 (en) | 2012-06-15 | 2017-09-19 | International Business Machines Corporation | Transactional processing |
| US9772854B2 (en) | 2012-06-15 | 2017-09-26 | International Business Machines Corporation | Selectively controlling instruction execution in transactional processing |
| US9811337B2 (en) | 2012-06-15 | 2017-11-07 | International Business Machines Corporation | Transaction abort processing |
| US10223214B2 (en) | 2012-06-15 | 2019-03-05 | International Business Machines Corporation | Randomized testing within transactional execution |
| US10430199B2 (en) | 2012-06-15 | 2019-10-01 | International Business Machines Corporation | Program interruption filtering in transactional execution |
| US10599435B2 (en) | 2012-06-15 | 2020-03-24 | International Business Machines Corporation | Nontransactional store instruction |
-
2006
- 2006-11-10 CN CNA2006101182445A patent/CN101178787A/en active Pending
Cited By (31)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9442737B2 (en) | 2012-06-15 | 2016-09-13 | International Business Machines Corporation | Restricting processing within a processor to facilitate transaction completion |
| US9442738B2 (en) | 2012-06-15 | 2016-09-13 | International Business Machines Corporation | Restricting processing within a processor to facilitate transaction completion |
| US9448796B2 (en) | 2012-06-15 | 2016-09-20 | International Business Machines Corporation | Restricted instructions in transactional execution |
| US9448797B2 (en) | 2012-06-15 | 2016-09-20 | International Business Machines Corporation | Restricted instructions in transactional execution |
| US9477514B2 (en) | 2012-06-15 | 2016-10-25 | International Business Machines Corporation | Transaction begin/end instructions |
| US9529598B2 (en) | 2012-06-15 | 2016-12-27 | International Business Machines Corporation | Transaction abort instruction |
| CN104364778B (en) * | 2012-06-15 | 2017-02-08 | 国际商业机器公司 | Saving/restoring selected registers in transactional processing |
| US9740549B2 (en) | 2012-06-15 | 2017-08-22 | International Business Machines Corporation | Facilitating transaction completion subsequent to repeated aborts of the transaction |
| US9740521B2 (en) | 2012-06-15 | 2017-08-22 | International Business Machines Corporation | Constrained transaction execution |
| US9766925B2 (en) | 2012-06-15 | 2017-09-19 | International Business Machines Corporation | Transactional processing |
| US9772854B2 (en) | 2012-06-15 | 2017-09-26 | International Business Machines Corporation | Selectively controlling instruction execution in transactional processing |
| US9792125B2 (en) | 2012-06-15 | 2017-10-17 | International Business Machines Corporation | Saving/restoring selected registers in transactional processing |
| US9811337B2 (en) | 2012-06-15 | 2017-11-07 | International Business Machines Corporation | Transaction abort processing |
| US9851978B2 (en) | 2012-06-15 | 2017-12-26 | International Business Machines Corporation | Restricted instructions in transactional execution |
| US9858082B2 (en) | 2012-06-15 | 2018-01-02 | International Business Machines Corporation | Restricted instructions in transactional execution |
| US9983881B2 (en) | 2012-06-15 | 2018-05-29 | International Business Machines Corporation | Selectively controlling instruction execution in transactional processing |
| US9983882B2 (en) | 2012-06-15 | 2018-05-29 | International Business Machines Corporation | Selectively controlling instruction execution in transactional processing |
| US9983883B2 (en) | 2012-06-15 | 2018-05-29 | International Business Machines Corporation | Transaction abort instruction specifying a reason for abort |
| US9983915B2 (en) | 2012-06-15 | 2018-05-29 | International Business Machines Corporation | Facilitating transaction completion subsequent to repeated aborts of the transaction |
| US9996360B2 (en) | 2012-06-15 | 2018-06-12 | International Business Machines Corporation | Transaction abort instruction specifying a reason for abort |
| US10185588B2 (en) | 2012-06-15 | 2019-01-22 | International Business Machines Corporation | Transaction begin/end instructions |
| US10223214B2 (en) | 2012-06-15 | 2019-03-05 | International Business Machines Corporation | Randomized testing within transactional execution |
| US10353759B2 (en) | 2012-06-15 | 2019-07-16 | International Business Machines Corporation | Facilitating transaction completion subsequent to repeated aborts of the transaction |
| US10430199B2 (en) | 2012-06-15 | 2019-10-01 | International Business Machines Corporation | Program interruption filtering in transactional execution |
| US10437602B2 (en) | 2012-06-15 | 2019-10-08 | International Business Machines Corporation | Program interruption filtering in transactional execution |
| US10558465B2 (en) | 2012-06-15 | 2020-02-11 | International Business Machines Corporation | Restricted instructions in transactional execution |
| US10599435B2 (en) | 2012-06-15 | 2020-03-24 | International Business Machines Corporation | Nontransactional store instruction |
| US10606597B2 (en) | 2012-06-15 | 2020-03-31 | International Business Machines Corporation | Nontransactional store instruction |
| US10684863B2 (en) | 2012-06-15 | 2020-06-16 | International Business Machines Corporation | Restricted instructions in transactional execution |
| US10719415B2 (en) | 2012-06-15 | 2020-07-21 | International Business Machines Corporation | Randomized testing within transactional execution |
| US11080087B2 (en) | 2012-06-15 | 2021-08-03 | International Business Machines Corporation | Transaction begin/end instructions |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101178787A (en) | Information communication method used for community old cadres health supervision | |
| CN101896886B (en) | Uniform synchronization between multiple kernels running on single computer systems | |
| US7810098B2 (en) | Allocating resources across multiple nodes in a hierarchical data processing system according to a decentralized policy | |
| US8571884B2 (en) | Healthcare communication and workflow management system and method | |
| CN105677431B (en) | Background work and foreground is decoupling | |
| CN1617501B (en) | Flexible architecture for notifying applications of state changes | |
| JP2650965B2 (en) | Computer system and task scheduling method thereof | |
| CN100485583C (en) | Power supply management system in parallel processing system and power supply management program therefor | |
| CN109814998A (en) | A kind of method and device of multi-process task schedule | |
| US20090165003A1 (en) | System and method for allocating communications to processors and rescheduling processes in a multiprocessor system | |
| US20080140857A1 (en) | Service-oriented architecture and methods for direct invocation of services utilizing a service requestor invocation framework | |
| US20070011227A1 (en) | System and method for providing direct web access to controllers in a process control environment | |
| US20080140759A1 (en) | Dynamic service-oriented architecture system configuration and proxy object generation server architecture and methods | |
| WO2014039312A1 (en) | Quota-based resource management | |
| US5991794A (en) | Component integration system for an application program | |
| US20090113457A1 (en) | Performing requested commands for model-based applications | |
| CN104536825B (en) | Lasting application activating and timer notice | |
| CN112230987B (en) | Distributed modular plug-in frame realization system and method | |
| WO2023011249A1 (en) | I/o multiplexing method, medium, device and operation system | |
| CN101414295A (en) | Method for upgrading database | |
| WO2023051034A1 (en) | Terminal code incremental compilation method, system, apparatus, server, and storage medium | |
| US9792419B2 (en) | Starvationless kernel-aware distributed scheduling of software licenses | |
| Karlsen | An Adaptive Transactional System–Framework and Service Synchronization | |
| Keayes et al. | Benefits of distributed HIS/RIS-PACS integration and a proposed architecture | |
| CN1697391A (en) | Method for implementing communication of information among multiple platforms |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |
Open date: 20080514 |