CN100401685C - Message interception generally used in network management and processing method therefor - Google Patents
Message interception generally used in network management and processing method therefor Download PDFInfo
- Publication number
- CN100401685C CN100401685C CNB2005100971209A CN200510097120A CN100401685C CN 100401685 C CN100401685 C CN 100401685C CN B2005100971209 A CNB2005100971209 A CN B2005100971209A CN 200510097120 A CN200510097120 A CN 200510097120A CN 100401685 C CN100401685 C CN 100401685C
- Authority
- CN
- China
- Prior art keywords
- message
- request
- module
- user
- orb
- 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
Abstract
The present invention discloses a message interception and processing method which is generally used for the network management. Based on a platform of common object request broker architecture (CORBA), after an object request broker (ORB) module is initialized, an application module registers a message capturer in the ORB module. The present invention also comprises that after the object request broker module receives the message, the registered message capturer is called to capture the received message; the message is processed according to an anticipated setting; the message is dispatched to a specific object in a portable object adaptor (POA) corresponding to the message for processing. By using the present invention, the processing procedures are simplified, can be maintained conveniently and have extensibility.
Description
Technical field
The present invention relates to the network management technology field, be meant that especially a kind of message general in network management intercepts and processing method.
Background technology
In the present webmaster solution based on common object request broker system (CORBA) bussing technique, what most of webmasters still adopted for the management of webmaster Operation Log and safety is to add the mode that log record or authorization check are handled code in application code.As: create a network element, network management system often need increase corresponding log processing code in order to write down this Operation Log in the application layer code that creates NE; Similarly in order to judge that whether current operation user has the operating right that creates NE, and then also need add the code of operating right verification in application code.And for example: the alarm shield switch that equipment is set, network management system is in the request of " alarm of shielding designated equipment " that receive the user, and before request is handed down to real physical equipment, system must carry out verification by first operating right to the user, confirm that the user possesses after the function that the alarm shield switch is set, can write down corresponding request information, just request can be handed down to network element device then, and the response message of synchronous waiting facilities, after the response or error messages that the equipment of receiving returns, system needs the result of recording operation once more, just operating result can be returned to the user at last.
In order better to say something, to be operating as example with " creating NE " in the transmission network management system below the prior art scheme is described.
After NMS user issued the operation requests that creates NE, network management system mainly needed to finish following three tasks:
1, whether the current operation of verification user has the operating right that creates NE;
If 2 authorization checks pass through, then begin the business processing flow that network element is created;
3, recording operation daily record comprises: need the record request parameter, as network element ID (ID), NE type etc., operate successfully details such as still failure.
Idiographic flow may further comprise the steps referring to shown in Figure 1:
After the operation requests that creates NE that send step 101～102, NMS user is distributed to network management system; Network management system is carried out the operating right verification, judges whether authorization check passes through, if, then enter step 103, otherwise, step 104 entered;
Step 103, network management system is carried out the business processing flow that network element is created according to this request that creates NE, and enters step 104 after finishing;
Step 104 writes down current Operation Log.
Present most of network management system still concentrates in the application layer code for these three task handling and finishes, promptly before handling request, insert the code of process user operating right verification, command word according to current transmission requesting users ID, current request, call the public function or the object method of safety management and judge whether the active user is allowed to carry out the request that creates NE, if error code is then directly returned in the authorization check failure; If authorization check passes through, then ask to be changed in the real business logic processing unit and handle; After request is finished dealing with, before request response is returned, need to insert code with the recording operation log information, needing decision operation during record is success or failure, need simultaneously required parameter is handled, here may need complicated parameter is carried out fluidization treatment, make it become exportable and readable character string, call the public function or the object method of log management then and finish the storehouse operation of daily record note.
There is following significant disadvantages in existing technology:
(1) software layer blurs.The prior art scheme need be added code to handle the problem of daily record and safety check in application layer code, therefore modules such as application layer Service Processing Module and daily record safety can't be kept apart, and can't guarantee the independence of service logic.
(2) difficult in maintenance.Because need in application layer code, insert the processing code of daily record and safety in each processing of request code; very loaded down with trivial details; and these processing codes can call the public function or the method for some daily records or safe handling usually; in case these public function parameters change, will bring the expense on a large amount of code maintenances undoubtedly.
(3) difficult treatment.The parameter of each operation all varies, this just means in order to write down the details of these operations, need increase code in application layer separates out and the parametric solution of operation according to certain regular character stringization, just can call public function or object method then and carry out record, this has directly increased the expense of handling, in case and these required parameters change or the form of record changes, correlative code also needs to revise thereupon.
(4) poor expandability.Based on the prior art scheme, also only be the problem that has solved log record and authorization check at present, and expanded function on this basis if desired, as calculate each request processing time, then need handle in the code in each request again and increase fresh code again to support new functional requirement, the non-constant of functional expansionary.
Summary of the invention
In view of this, the object of the present invention is to provide message general in a kind of network management to intercept and processing method, make that above-mentioned processing is simpler, be convenient to safeguard and have extensibility.
Intercept and processing method based on general message in above-mentioned purpose a kind of network management provided by the invention, based on common object request broker system CORBA platform, after the ORB of Object Request Broker module initialization, application module is registered a message acquirer in the ORB module; And further comprise:
A. after Object Request Broker's module received message, the message acquirer that calls registration was intercepted and captured the message of described reception;
B. according to setting in advance the message of handling described intercepting and capturing, described processing comprises: the operation of log record or concentrated authentication or message modification; The method of carrying out described operation employing comprises: the correlating method of employing dynamic message analytic method or portable object adapter and user's characteristic information is carried out the operation of described log record or concentrated authentication, adopts the message context processing method to carry out the operation of described message modification;
C. the described message that sets in advance after the processing is dispatched to the concrete object among the portable object adapter POA of this message correspondence and handle.
This method step B further comprises:
B11. use dynamic Any technology that the data of the Any type that comprises in this message are resolved, and convert the readable character string information of user to;
B12. the character string information that obtains is recorded in the journal file.
The described message of this method is request message, after the Servant object disposes to request message, response message further comprises before sending to client's side: the POA message call is intercepted and captured the response message that device is intercepted and captured this request message, and response message is made amendment or log record.
The described message of this method is request message, and the data of the Any type that comprises in the described message comprise: request ID, action name, required parameter and operation return value;
Described message is response message, and the data of the Any type that comprises in the described message comprise: request ID, action name, required parameter, operation return value and response data;
Described message is unexpected message, and the data of the Any type that comprises in the described message comprise: request ID, action name, required parameter, operation return value and operation exception information.
The message of the described intercepting and capturing of this method step A is request message, and step B further comprises:
B21. the POA name under the request of obtaining;
B22. verify according to the name of POA under the request message that obtains whether the user of this client's side has this operation permission of being asked, if the POA under this request message dispatches this request message to the Servant class of correspondence and handles; Otherwise, dish out and illegally call unexpected message.
This method further comprises: the newly-built POA who is used to handle this user's request of user that is connected to this system in advance for each; Wherein, described POA name is identical with user's name.
The message of the described intercepting and capturing of this method step A is request message, and step B further comprises:
B31. service context of initialization;
B32. obtain the current time in system;
B33. the current time in system is added in the middle of the parameter of described service context;
B34. this service context is added in the request message and go;
The POA of B35.ORB module dispatches described request message to affiliated Servant object, and the Servant object is finished the processing to this request message;
The B36.ORB module is intercepted and captured the request response after this request message is finished dealing with;
B37. obtain the service specified context object in the request response;
B38. obtain the current time in system;
B39. according to the time parameter that comprises in current system time and the service specified context object, computation requests is from receiving the time of finishing dealing with and being spent.
Obtain the process of current time in system described in this method step B32 and the B38 and obtain the current time in system for the system function that itself provides by the call operation system.
The described computational process of this method step B39 comprises that current system time is deducted the indicated time of time parameter that comprises in the service context object obtains asking time of finishing dealing with and being spent from receiving.
From such scheme as can be seen, the present invention directly adopts the POA tree structure to discern the initiation object of request, promptly be who has initiated this operation requests, the information that does not need subsidiary request user ID in the required parameter, if authorization check failure simultaneously, can directly message be returned, and not need message is continued to be transmitted to application layer process, thereby save overhead.Can directly obtain the type of asking title, required parameter information and required parameter by the message Interception Mechanism of CORBA simultaneously, promptly be the two-way parameter of input parameter, output parameter or input and output, distinguish different requests and no longer need to attach in the operating parameter request command word information.
Directly utilize the message Interception Mechanism of CORBA to activate request or response message, in conjunction with the dynamic Any technology of CORBA the required parameter information, response parameter information, return value or the abnormal information that comprise in the message are resolved then, and according to self-defining record format warehousing, application layer does not need to pay close attention to the thing of operation log recording fully, only need pay close attention in the processing of service logic, thereby system framework and application layer are separated.
Utilize CORBA message Interception Mechanism to make amendment, increase some request custom context parameters, just can guarantee expanded function on the basis that does not influence existing capability and existing application layer process logic the message that activates.Typically handle the context parameters that returns institute's spended time from receiving as in request, inserting the user record request.
Description of drawings
Fig. 1 is the schematic flow sheet of the operation that creates NE in the existing transmission network management system;
Fig. 2 is the schematic flow sheet of embodiment of the invention message acquirer registration process;
Fig. 3 is the schematic flow sheet of embodiment of the invention log processing process;
Fig. 4 is the schematic flow sheet of embodiment of the invention safety check processing procedure;
Fig. 5 is the schematic flow sheet of embodiment of the invention expanded application processing procedure.
Embodiment
In fact, for for the network management system of CORBA bussing technique, the CORBA technology itself provides a kind of message Interception Mechanism (Intercept), utilize this mechanism can interception system the request and the response message of contact, based on the message of being intercepted and captured, can realize the record of Operation Log, the processing such as verification of operating right with a kind of universal mode fully, thereby log record and authorization check can be shielded fully in the system bottom framework and realize that application layer can be comprehended and be absorbed in the realization of service logic.
Therefore the present invention program's core is based on the CORBA system platform, and after Object Request Broker (ORB) module initialization, application module is registered a message acquirer in the ORB module; And further comprise: after the ORB module received message, the message acquirer that calls registration was intercepted and captured the message of described reception; Handle described message according to setting in advance; The concrete object of more described message being dispatched in the portable object adapter (POA, Portable Object Adapter) to this message correspondence is handled.
Below the functional module in the existing CORBA system involved among the present invention is described.
1, ORB intercepts and captures device mechanism functional module, and mainly comprise: functions such as registration, service context definition are registered/gone to ORB initialization, message acquirer.Below the related in the present invention several classes of this module are described.
1) ORB module (Module), here in fact ORB Module is not a class, but represent all ORB API, here for convenience of description, the interface class of regarding as with whole ORB module abstracts, inner actual detail specifically can be with reference to the technical manual of OMGCORBA standard or relevant ORB product not within the scope that the present invention relates to.
2) ORB_Init class, represent a function class of network management system bottom frame layer, mainly finish the function relevant to the initialization of ORB platform and configuration etc., function related to the present invention is Init, the environment that initialization bottom ORB platform is relevant, as: device registration, POA activation etc. intercepted and captured.
3) Server_Request_Interceptor class, expression CORBA message acquirer is mainly finished the intercepting and capturing to request message, response message and abnormal information.Wherein, include intercepting and capturing request message receive_request, intercepting and capturing response message send_reply, intercepting and capturing unexpected message send_exception.
4) PortableInterceptior::ORB_initInfo class, the information that record is relevant with the ORB initialization with management.Contain registration message and intercept and capture device add_server_request_interceptor.
5) Server_ORBInitializer class, the initialized assisted class of expression ORB_core object instance is mainly handled the relevant task of some initialization of ORB_core object instance initialization front and back.Include pre_init: handle ORB_core object instance initialization task before; And post_init, handle ORB_core object instance initialization task afterwards.
6) PortableInterceptor::ServerRequestInfo class is the entity class of expression solicited message.
Comprise: add_reply_serive_context, add request respond services context parameters;
Get_reply_service_context obtains request respond services context parameters;
Adapter_name obtains the name of asking place POA;
Sending_exception obtains abnormal information;
Request_id obtains request ID;
Arguments obtains required parameter information;
Operation obtains the request title;
Reply_status obtains the request responsive state;
Result obtains request results.
7) IOP::ServiceContext class is used for increasing or obtaining the service context parameter information in request, is a structure.
Conclude ORB and intercept and capture the related in the present invention class of device mechanism functional module, ginseng is shown in Table 1:
| Class | Attribute | |
| 1 | ORB Module | ORB_init |
| 2 | ORBInit | Init |
| 3 | Server_Request_Interceptor | receive_request send_reply send_exception |
| 4 | PortableInterceptor::ORB_initInfo | add_server_request_interceptor |
| 5 | Server_ORBInitializer | pre_init post_init |
| 6 | PortableInterceptor::ServerRequestInfo | add_reply_serive_context get_reply_service_context adapter_name sending_exception request_id arguments operation reply_status result |
| 7 | IOP::ServiceContext |
Table 1
2, daily record and safety management function module:
This module mainly is to realize that by the webmaster application layer major function comprises: to intercepting and capturing the device intercepted message, comprise that request message, response message, unexpected message etc. resolve, generate corresponding log record; Request captured is judged its user's operating right earlier, whether this request scheduling is arrived the processing program in decision then.Below the related in the present invention several classes of this module are described.
8) TALogMgr class is the log management class, finishes the log management associative operation.
Main method wherein comprises: TAWriteOperLog, recording operation daily record;
GetOperLogRecord obtains the required information of log record item from the message of intercepting and capturing;
WriteOperLogRecord, the storehouse operation of daily record note.
9) TALogHelper class is the daily record assisted class, finishes the relevant miscellaneous function of log management.
Main method wherein comprises: ParseAnyData, use the dynamic Any technology of CORBA that the data message that comprises in the message is resolved;
ParseException: resolve the data message in the unexpected message.
10) TASecurityMgr class realizes verification and management function to operating right.
Wherein main method comprises: Verify, whether verified users possesses a certain operation permission, promptly directly judge according to request captured message whether the user possesses this operation permission of execution, and authorization check passes through, and then request is transmitted to concrete request processing module; Otherwise abandon this request message or directly return failure response message.
11) servo (Servant) class, the Servant class among the expression CORBA, the i.e. class of the concrete process object request of application layer.
Wherein mainly comprise: OperationImpl, expression requested service logical process method.
Conclude daily record and the related in the present invention class of safety management function module, ginseng is shown in Table 2:
| Class | Method | |
| 8 | TALogMgr | TAWriteOperLog GetOperLogRecord WriteOperLogRecord |
| 9 | TALogHelper | ParseAnyData ParseException |
| 10 | TASecurityMgr | Verify |
| 11 | Servant | OperationImpl |
Table 2
This programme is handled realization flow and is mainly comprised: message acquirer register flow path, log processing flow process, several parts of safety check flow process, set forth respectively below.
Registration message is intercepted and captured device:
Mainly finish the ORB initialization procedure earlier, and then in ORB the registration message acquirer object, each like this when ORB when local terminal or far-end receive CORBA message, wherein CORBA message may be request message, response message, unexpected message etc., ORB can adjust back the corresponding message treatment method of this message acquirer object automatically, and then finishes message to the conversion of daily record or the verifying function of operating right by the method for log processing flow process or safety check flow process part.
Referring to shown in Figure 2, specifically may further comprise the steps:
Step 204 can be called pre_init and the post_init method of Server_ORBInitializer successively in the initialized process of ORB;
The log processing flow process:
This flow process is mainly driven by message acquirer, after message acquirer intercepts message, can adjust back the corresponding object method of log management module, come the request ID, action name, required parameter, response data (for response message), operation return value, the operation exception information data messages such as (to unexpected messages) that comprise in this message are resolved, and convert the readable character string information of user to, record in the journal file then.After log processing was finished, the intercepting and capturing device continues message to be dispatched to corresponding request processing module again to be handled.It also is similar handling for response message and unexpected message, handles before response message sends in request, and message acquirer is intercepted and captured message earlier, carries out sending out after the log processing again.
Concrete treatment step comprises:
Also can adopt with quadrat method in to the processing procedure of response message and unexpected message and carry out log record, the process of concrete log record and the handling process basically identical of request message repeat no more here.
Safety check handling process and log processing flow process all fours, promptly after ORB receives request message, adjust back the method for message acquirer object earlier, message is given to the processing of intercepting and capturing the advanced line operate authorization check of device, after handling again the result's decision according to authentication whether continue to transmit message or directly return mistake.
Concrete processing sequence figure and step are as follows:
Here need to prove that the name of the POA here is the same with user's name, that is to say that supposing the system is connected to the newly-built sub-POA of user of this system for each here, all requests that this user sends are all dispatched to this POA and are handled.If system adopts this POA administrative mechanism, then need in required parameter, transmit corresponding user ID, have two kinds of schemes selective: the one, the direct parameter that in required parameter, increases a user ID; The 2nd, by client's example before request sends earlier with Request Interception, and in request, increase a request service context, put into the user ID parameter in this context.The step that specific implementation method and " expanded application " part is described is similar, and difference is that this message intercepts and captures before being sent by client's side.
Step 403, Server_Request_Interceptor calls the verify method of TASecurityMgr and verifies according to the name of POA under the request of obtaining whether the user has this operation permission, if enter step 406; Otherwise, enter step 404.
A simple expanded application of the main description on CORBA message of expanded application handling process Interception Mechanism promptly realizes coming computation requests to handle the function of the time that is spent by modify request messages.Main principle is after message acquirer is truncated to request message, in request message, insert a request contexts object earlier, the time that the record request message sink arrives, wait request to finish dealing with then, when application layer was returned response message, message acquirer was intercepted and captured response message once more, and the request contexts of inserting before in the message is taken out, compare with the capture time of current response message, can calculate this operation and spend how many processing times altogether.
Concrete processing sequence figure and step are as follows:
Step 505, the add_reply_service_context method that Server_Request_Interceptor calls PortableInterceptor::RequestInfo are added this service context ServiceContext in the request message to and are gone.
Technical solution of the present invention has reduced the coupled relation between the system module, adopts general tupe to effectively reduce the maintenance workload of system simultaneously and safeguards complexity, and the system that makes possesses good extensibility.
The above only is preferred embodiment of the present invention, and is in order to restriction the present invention, within the spirit and principles in the present invention not all, any modification of being done, is equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (9)
1. general message is intercepted and processing method in the network management, it is characterized in that based on common object request broker system platform, after Object Request Broker's module initialization, application module is registered a message acquirer in Object Request Broker's module; And further comprise:
A. after Object Request Broker's module received message, the message acquirer that calls registration was intercepted and captured the message of described reception;
B. according to setting in advance the message of handling described intercepting and capturing, described processing comprises: the operation of log record or concentrated authentication or message modification; The method of carrying out described operation employing comprises: the correlating method of employing dynamic message analytic method or portable object adapter and user's characteristic information is carried out the operation of described log record or concentrated authentication, adopts the message context processing method to carry out the operation of described message modification;
C. the described message that sets in advance after the processing is dispatched to the concrete object in the portable object adapter of this message correspondence and handle.
2. method according to claim 1 is characterized in that step B further comprises:
B11. use dynamic Any technology that the data of the Any type that comprises in this message are resolved, and convert the readable character string information of user to;
B12. the character string information that obtains is recorded in the journal file.
3. method according to claim 2, it is characterized in that, described message is request message, after target servo disposes to request message, response message further comprises before sending to client's side: the portable object adapter message call is intercepted and captured the response message that device is intercepted and captured this request message, and response message is made amendment or log record.
4. according to claim 2 or 3 described methods, it is characterized in that described message is request message, the data of the Any type that comprises in the described message comprise: request mark, action name, required parameter and operation return value;
Described message is response message, and the data of the Any type that comprises in the described message comprise: request mark, action name, required parameter, operation return value and response data;
Described message is unexpected message, and the data of the Any type that comprises in the described message comprise: request mark, action name, required parameter, operation return value and operation exception information.
5. method according to claim 1 is characterized in that the message of the described intercepting and capturing of steps A is request message, and step B further comprises:
B21. the portable object adapter name under the request of obtaining;
B22. verify according to the name of portable object adapter under the request message that obtains whether the user of this client's side has this operation permission of being asked, if the portable object adapter under this request message is dispatched this request message to the servo class of correspondence and is handled; Otherwise, dish out and illegally call unexpected message.
6. method according to claim 5 is characterized in that, this method further comprises: the newly-built portable object adapter that is used to handle this user's request of user that is connected to this system in advance for each;
Wherein, described portable object adapter name is identical with user's name.
7. method according to claim 1 is characterized in that the message of the described intercepting and capturing of steps A is request message, and step B further comprises:
B31. service context of initialization;
B32. obtain the current time in system;
B33. the current time in system is added in the middle of the parameter of described service context;
B34. this service context is added in the request message and go;
B35. the portable object adapter of Object Request Broker's module dispatches described request message to affiliated target servo, and target servo is finished the processing to this request message;
B36. Object Request Broker's module is intercepted and captured the request response after this request message is finished dealing with;
B37. obtain the service specified context object in the request response;
B38. obtain the current time in system;
B39. according to the time parameter that comprises in current system time and the service specified context object, computation requests is from receiving the time of finishing dealing with and being spent.
8. method according to claim 7 is characterized in that, obtains the process of current time in system described in step B32 and the B38 and obtains the current time in system for the system function that itself provides by the call operation system.
9. method according to claim 7 is characterized in that, the described computational process of step B39 comprises that current system time is deducted the indicated time of time parameter that comprises in the service context object obtains asking time of finishing dealing with and being spent from receiving.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100971209A CN100401685C (en) | 2005-12-30 | 2005-12-30 | Message interception generally used in network management and processing method therefor |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100971209A CN100401685C (en) | 2005-12-30 | 2005-12-30 | Message interception generally used in network management and processing method therefor |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1852142A CN1852142A (en) | 2006-10-25 |
| CN100401685C true CN100401685C (en) | 2008-07-09 |
Family
ID=37133612
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100971209A Expired - Fee Related CN100401685C (en) | 2005-12-30 | 2005-12-30 | Message interception generally used in network management and processing method therefor |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100401685C (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103440297A (en) * | 2013-08-20 | 2013-12-11 | 苏州迈科网络安全技术股份有限公司 | Method for recording and reading user operation log information |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6839708B1 (en) * | 2002-02-26 | 2005-01-04 | Sprint Communication Company L.P. | Computer system having an authentication and/or authorization routing service and a CORBA-compliant interceptor for monitoring the same |
-
2005
- 2005-12-30 CN CNB2005100971209A patent/CN100401685C/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6839708B1 (en) * | 2002-02-26 | 2005-01-04 | Sprint Communication Company L.P. | Computer system having an authentication and/or authorization routing service and a CORBA-compliant interceptor for monitoring the same |
Non-Patent Citations (14)
| Title |
|---|
| Common Object RequestBrokerArchitecture:CoreSpecification. OMG.. 2004 |
| Common Object RequestBrokerArchitecture:CoreSpecification. OMG.. 2004 * |
| CORBA中实现安全代理的截获器研究. 陈明峰，尹刚，吴泉源.计算机应用研究，第8期. 2004 |
| CORBA中实现安全代理的截获器研究. 陈明峰，尹刚，吴泉源.计算机应用研究，第8期. 2004 * |
| CORBA可移植拦截器及其应用. 吴琦，郎波，张鑫，李伟琴.计算机工程与应用，第34期. 2004 |
| CORBA可移植拦截器及其应用. 吴琦，郎波，张鑫，李伟琴.计算机工程与应用，第34期. 2004 * |
| CORBA系统中截获机制研究与实现. 汪芸，宋光磊.东南大学学报(自然科学版)，第32卷第6期. 2002 |
| CORBA系统中截获机制研究与实现. 汪芸，宋光磊.东南大学学报(自然科学版)，第32卷第6期. 2002 * |
| CORBA系统中请求级截获器的设计与实现. 尹刚，王怀民，滕猛.计算机工程与设计，第23卷第3期. 2002 |
| CORBA系统中请求级截获器的设计与实现. 尹刚，王怀民，滕猛.计算机工程与设计，第23卷第3期. 2002 * |
| 分布式诊断系统的请求调度模型. 王海峰，阳建宏，杨德斌，徐金梧.计算机工程，第31卷第7期. 2005 |
| 分布式诊断系统的请求调度模型. 王海峰，阳建宏，杨德斌，徐金梧.计算机工程，第31卷第7期. 2005 * |
| 基于CORBA截获器实现隐式事务传播. 张静，王庆大，王海洋.计算机应用，第23卷. 2003 |
| 基于CORBA截获器实现隐式事务传播. 张静，王庆大，王海洋.计算机应用，第23卷. 2003 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1852142A (en) | 2006-10-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104243154B (en) | Server user's permission centralized control system and method | |
| US6889378B2 (en) | Information processing method, inter-task communication method, and computer-executable program for the same | |
| CN103927218B (en) | Event distributing method and system | |
| US5764898A (en) | System for task tracking and controlling electronic mail | |
| CN104216912A (en) | Method and device for achieving non-intrusive service form workflow | |
| JP2005158066A (en) | Automated customer entitlement system for vendor services | |
| CN112100262A (en) | Method and system for quickly building and dynamically expanding multi-tenant software as a service (SaaS) platform | |
| CN102081554A (en) | Cloud computing operating system as well as kernel control system and method thereof | |
| CN105119966A (en) | Official account management method and device | |
| US8195566B2 (en) | Web service interfaces used in providing a billing service | |
| CN101179622A (en) | Multi-order processing arrangement in communication system and processing method thereof | |
| CN107070894A (en) | A kind of software integrating method based on enterprise's cloud service platform | |
| CN100488199C (en) | Media issuing system and method | |
| WO2023093039A1 (en) | Inter-process communication method and system | |
| US6141679A (en) | High performance distributed transaction processing methods and apparatus | |
| CN110069909A (en) | It is a kind of to exempt from the close method and device for logging in third party system | |
| CN103379093B (en) | A kind of method and device for realizing account intercommunication | |
| CN106095424B (en) | The treating method and apparatus for calling of trading in application component | |
| WO2020124991A1 (en) | Cloud kernel-based receiving terminal system | |
| CN100401685C (en) | Message interception generally used in network management and processing method therefor | |
| CN115439254B (en) | Financial background transaction platform with intelligent key function | |
| US8458716B2 (en) | Enterprise resource planning with asynchronous notifications of background processing events | |
| CN106301881A (en) | A kind of method and device for business processing | |
| US7743117B2 (en) | Service provisioning method, system and computer program product | |
| CN115941782A (en) | Message pushing method and system based on RPA and chat robot |
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 | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20080709 Termination date: 20141230 |
|
| EXPY | Termination of patent right or utility model |