WO2000054150A2 - Verfahren zur nachrichtenübertragung zwischen einer einem ersten prozess zugewiesenen clientinstanz und wenigstens einer mindestens einem weiteren prozess zugewiesenen serverinstanz innerhalb eines verteilten systems - Google Patents
Verfahren zur nachrichtenübertragung zwischen einer einem ersten prozess zugewiesenen clientinstanz und wenigstens einer mindestens einem weiteren prozess zugewiesenen serverinstanz innerhalb eines verteilten systems Download PDFInfo
- Publication number
- WO2000054150A2 WO2000054150A2 PCT/DE2000/000623 DE0000623W WO0054150A2 WO 2000054150 A2 WO2000054150 A2 WO 2000054150A2 DE 0000623 W DE0000623 W DE 0000623W WO 0054150 A2 WO0054150 A2 WO 0054150A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- instance
- client
- server
- message
- action
- Prior art date
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/547—Remote procedure calls [RPC]; Web services
- G06F9/548—Object oriented; Remote method invocation [RMI]
Definitions
- the invention relates to a method for message transmission between a client instance assigned to a first process and at least one server instance assigned to at least one further process within a distributed system.
- Distributed systems preferably play a special role in today's telecommunications systems, which are generally multiprocessor systems.
- a distributed system is characterized in particular by the fact that processes can each be assigned to different processors, the processors possibly being located on spatially separate platforms in the distributed system.
- One of the most important aspects in the communication between different processes of a distributed system is the platform transparency. This means that a process that wants to send a message to another process does not have to know the platform on which the other process is currently running.
- Such a complex distributed system must meet many other requirements today. Among other things, it must prove to be extremely reliable, as flexible as possible and open to adjustments and extensions.
- the software of such a complex distributed system should therefore be designed to be highly modular with firmly defined open interfaces to the outside, so that the individual modules of the software are easily adaptable and, above all, reusable.
- Implicit concurrency There are two ways to implement implicit concurrency:
- - Passive objects An asynchronous message exchange is converted into a sequential synchronous method or procedure call. The parallel processing of the objects communicating with each other is very limited.
- Active objects A process is started for each object. This procedure leads to high resource consumption and can therefore only be realized with a limited number of objects.
- the object of the invention is therefore to design a method for message transmission between so-called different processes assigned client and server instances of a distributed system in such a way that the implementation of the method is as high as possible reusable and at the same time the maintainability is facilitated as much as possible.
- this is achieved by assigning a first process for message transmission between A client instance and at least one server instance assigned to at least one further process within a distributed system can also be used as partner instances provided as mutual communication partners.
- a first instance of the partner instances containing the first process selects at least one suitable further instance of the partner instances containing the at least one further process for message acceptance and forwarding.
- the further instance containing at least one further process forwards this message to at least one server instance addressed by it and optionally receives a message from the at least one server instance for forwarding to the client instance via the first instance containing the first process.
- the definition of the type of communication between the client instance and the at least one server instance is shifted to the partner instances containing a process and intended as mutual communication partners.
- the messages between the client instance and the first instance containing the first process and between the at least one server instance and the further instance containing at least one further process are synchronized, e.g. transmitted by procedure or method call.
- the message transmission between a first instance containing the first process and a further instance containing at least one further process can then take place asynchronously or synchronously, decoupled from the communication interfaces of the client instance and at least one server instance. This ensures maximum reusability, primarily with regard to the implementation of the client and at least one server instance.
- the maintainability is also considerably improved in that at most the communication interfaces between the first process containing the first process
- a further advantageous embodiment of the invention provides that the first instance containing the first process makes the selection of the further instance containing at least one further process on the basis of an assignment table.
- the type of messages that can be sent by the client instance and the address of the further instance containing at least one further process are entered in this assignment table.
- An assignment table has the advantage that its content can be changed at any time and enables the first instance containing the first process to be selected quickly.
- the selection made by the first instance containing the first process can be changed dynamically depending on the system load. This prevents system crashes and deadlocks when the processes are allocated to the processors.
- Another embodiment of the invention relates to the special case that the first process and the at least one further process coincide.
- the first instance containing the first process and the further instance containing the at least one further process are combined in one instance.
- the method according to the invention can be applied to this special case without adjustments.
- All instances can be implemented in the form of objects, the structure of which is determined by object classes.
- the first instance containing the first process and the further instance containing at least one further process preferably each have the structure of a common object. class. In this way, the principles of purely object-oriented programming are exploited, resulting in a high degree of modularity, high reusability and maintainability.
- Another embodiment of the invention can be seen in a very expedient use of the method according to the invention on a telephone switching system. Accordingly, all of the advantages mentioned above also come into play in connection with a telephone switching system.
- FIG. 1 shows an exemplary flow chart of the method according to the invention
- Figure 2 shows an application example in the area of a system alarm in a telecommunications system such as a telephone switching system
- FIG. 1 describes in a flowchart the message transmission between a client instance assigned to a first process and a server instance assigned to a further process.
- the instances client, server, the first instance containing the first process and the further instance containing the at least one further process, and the action which is carried out by the server instance are represented in the form of objects with boxes.
- the Client object corresponds to a client instance
- the Server object corresponds to a server instance
- the ObjectHandler1 object corresponds to a first active instance containing the first process.
- partner instances provided, the object ObjectHandler2 of a further active instance of the partner instances containing the further process, the object action of an action and the object confirmation action of a feedback action on a requested action.
- the active instances that contain the respective processes are identified by boxes with bold lines. The type of action is only determined when the special Action object is called.
- a client requests an action from the server, on which one
- the client calls the action and does not have to know which process or on which processor platform the action is to be carried out.
- the object handler provides the client with the invoke_action call procedure.
- the ObjectHandler1 is assigned a unique number (get handle number) and a timer is started (start timer), which triggers an error handling if the feedback does not arrive in time .
- the ObjectHandler searches for a partner instance intended as a communication partner, for example ObjectHandler2 (find target ObjectHandler), which is assigned to the action depending on the type of action, and transmits the message of the action request action_request to the ObjectHandler2.
- the ObjectHandler2 accepts the message, stores the address of its communication partner Objecthandlerl (disrupt communication partner) together with the number clearly assigned to the ObjectHandlerl and executes the procedure of the Action object (execute).
- the Action object then causes the server addressed by the client to execute the action by calling the action procedure.
- the Server in an analogous way indirectly returns feedback to the client. Accordingly, the following procedure calls, message transfers and actions run from the server towards the client.
- Procedure call Invoke_action delete address of the communication partner and transfer of the action request message for the feedback action_request from ObjectHandler2 to ObjectHandlerl, which is known to ObjectHandler2 due to the assigned number, ObjectHandlerl deletes the assigned number (release handle number) and stops the timer (stop timer), to transmit the feedback, Objecthandlerl calls the execute procedure of the Confirm Action object and lastly, the Conform Action object executes the client's confirm_action procedure.
- the inventive method of message transmission from the client to the server proceeds in a similar manner to that described above. There are no steps like get handle number, start timer, disturb communication partner and the steps regarding the feedback from the server towards the client.
- the ObjectHandlerl will either pass the action_request message to an ObjectHandler2 and the ObjectHandler2 ensures that the action is carried out by several servers, or the ObjectHandlerl sends several action_request messages to several ObjectHandler2 containing the server process, each of which causes the server to execute the action.
- the ObjectHandlerl sends several action_request messages to several ObjectHandler2 containing the server process, each of which causes the server to execute the action.
- a combination of the two variants mentioned is also possible.
- the ObjectHandlerl is used in each case send an action_request message to the ObjectHandler2 containing the different processes and the ObjectHandler2 each cause the server to execute the action.
- each server can also act as a client and each client can also act as a server, and client and server function can be combined in one object.
- the objects ObjectHandlerl and ObjectHandler2 are combined into a single object.
- the ObjectHandler1 sends the action_request message to itself in this case.
- Figure 2 shows an application example in the area of a system alarm in a telecommunication system e.g. a telephone switching system.
- An alarm balance monitor (ABM) object has the task of drawing an alarm balance sheet for all alarms of the alarmable instances (AMOI) it monitors.
- the alarm balance monitor requires at least one so-called SIBS object, which is located on a processor platform and provides it with a collected information relating to the monitored alarmable instances.
- the boxes represent the objects Caller, AMOI (AlarmManagerObjectInstance), SIBS (SiteBalanceSupply) and ABM (AlarmBalanceMonitor).
- the arrows can be used to transmit messages across process boundaries indicated the objects.
- the message transmission corresponds to the message transmission between client and server described in FIG. 1.
- the Caller object can act as a client and the AMOI object as a server.
- a monitored alarmable instance AMOI receives a new alarm from a caller, checks the parameters determining the alarm (checkjparams) and creates a new alarm instance (create contained alarm).
- - Confirm A feedback from the instance AMOI to the instance Caller after the system alarm call set_alarm.
- At least one server object SIBS is requested to collect the information required for the alarm balance (aecumulate alarm status of all associated AMOI).
- the server object ABM is then requested to receive the at least one SIBS object Collect information for the alarm balance (accumulate alarm status of all associated SIBS).
- the messages are transmitted from one object to another object via an active first instance and via an active further partner instance, e.g. via the ObjectHandler1 and via the ObjectHandler2 from FIG. 1, both of which are not shown in FIG. 2.
- the selection of the object handler 2 made by the ObjectHandler 1 can be made on the basis of an assignment table.
- the assignment table looks like this, for example:
- the assignment of the ObjectHandler2 can be changed depending on the system load.
Abstract
Description
Claims
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE10080578T DE10080578D2 (de) | 1999-03-09 | 2000-03-01 | Verfahren zur Nachrichtenübertragung zwischen einer einem ersten Prozess zugewiesenen Clientinstanz und wenigstens einer mindestens einem weiteren Prozess zugewiesenen Serverinstanz innerhalb eines verteilten Systems |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
DE1999110345 DE19910345A1 (de) | 1999-03-09 | 1999-03-09 | Verfahren zur Nachrichtenübertragung zwischen einer einem ersten Prozeß zugewiesenen Clientinstanz und wenigstens einer mindestens einem weiteren Prozeß zugewiesenen Serverinstanz innerhalb eines verteilten Systems |
DE19910345.3 | 1999-03-09 |
Publications (3)
Publication Number | Publication Date |
---|---|
WO2000054150A2 true WO2000054150A2 (de) | 2000-09-14 |
WO2000054150A3 WO2000054150A3 (de) | 2001-04-05 |
WO2000054150A9 WO2000054150A9 (de) | 2001-09-20 |
Family
ID=7900257
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/DE2000/000623 WO2000054150A2 (de) | 1999-03-09 | 2000-03-01 | Verfahren zur nachrichtenübertragung zwischen einer einem ersten prozess zugewiesenen clientinstanz und wenigstens einer mindestens einem weiteren prozess zugewiesenen serverinstanz innerhalb eines verteilten systems |
Country Status (3)
Country | Link |
---|---|
CN (1) | CN1350673A (de) |
DE (2) | DE19910345A1 (de) |
WO (1) | WO2000054150A2 (de) |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0623876A2 (de) * | 1993-04-30 | 1994-11-09 | International Business Machines Corporation | Vorrichtung und Verfahren zur Bindung von Objektverwaltern für kooperative Verarbeitung in einer Objektorientierten Rechnerumgebung |
GB2305270A (en) * | 1995-09-15 | 1997-04-02 | Ibm | Bridge for a client-server environment |
WO1998002814A1 (en) * | 1996-07-15 | 1998-01-22 | Next Software, Inc. | Method and apparatus for dynamically brokering object messages among object models |
EP0834807A1 (de) * | 1996-08-26 | 1998-04-08 | Tandem Computers Incorporated | Verfahren und Gerät zur Durchführung von effizienten CORBA-Transaktionen |
EP0860776A1 (de) * | 1997-02-19 | 1998-08-26 | Hitachi, Ltd. | Interobjekt-Kommunikationsverfahren |
US5802367A (en) * | 1995-07-07 | 1998-09-01 | Microsoft Corporation | Method and system for transparently executing code using a surrogate process |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5329619A (en) * | 1992-10-30 | 1994-07-12 | Software Ag | Cooperative processing interface and communication broker for heterogeneous computing environments |
US6446204B1 (en) * | 1997-10-31 | 2002-09-03 | Oracle Corporation | Method and apparatus for implementing an extensible authentication mechanism in a web application server |
-
1999
- 1999-03-09 DE DE1999110345 patent/DE19910345A1/de not_active Withdrawn
-
2000
- 2000-03-01 WO PCT/DE2000/000623 patent/WO2000054150A2/de active Application Filing
- 2000-03-01 CN CN 00807384 patent/CN1350673A/zh active Pending
- 2000-03-01 DE DE10080578T patent/DE10080578D2/de not_active Expired - Fee Related
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0623876A2 (de) * | 1993-04-30 | 1994-11-09 | International Business Machines Corporation | Vorrichtung und Verfahren zur Bindung von Objektverwaltern für kooperative Verarbeitung in einer Objektorientierten Rechnerumgebung |
US5802367A (en) * | 1995-07-07 | 1998-09-01 | Microsoft Corporation | Method and system for transparently executing code using a surrogate process |
GB2305270A (en) * | 1995-09-15 | 1997-04-02 | Ibm | Bridge for a client-server environment |
WO1998002814A1 (en) * | 1996-07-15 | 1998-01-22 | Next Software, Inc. | Method and apparatus for dynamically brokering object messages among object models |
EP0834807A1 (de) * | 1996-08-26 | 1998-04-08 | Tandem Computers Incorporated | Verfahren und Gerät zur Durchführung von effizienten CORBA-Transaktionen |
EP0860776A1 (de) * | 1997-02-19 | 1998-08-26 | Hitachi, Ltd. | Interobjekt-Kommunikationsverfahren |
Also Published As
Publication number | Publication date |
---|---|
WO2000054150A9 (de) | 2001-09-20 |
DE19910345A1 (de) | 2000-09-21 |
CN1350673A (zh) | 2002-05-22 |
WO2000054150A3 (de) | 2001-04-05 |
DE10080578D2 (de) | 2002-03-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
DE69530734T2 (de) | System und Verfahren zur Workflow-Verwaltung | |
DE69728601T2 (de) | Client-Server-Architektur mit nebenläufigen Servern | |
DE602005004334T2 (de) | Nms zur Verarbeitung von Multi-Server Ereignissen | |
DE69734432T2 (de) | Verfahren und Vorrichtung zur Absendung von Clientverfahrenanrufen in einem Server Rechnersystem | |
DE19511770B4 (de) | Datensuchsystem sowie Verfahren zum Nachrüsten eines solchen | |
DE112008002439T5 (de) | Architektur und Protokoll für die erweiterbare und skalierbare Kommunikation | |
DE102005016587B4 (de) | Verfahren zum Bilden einer gemeinsamen Kommunikationssitzung, Verfahren zum Bilden einer ersten Kommunikationssitzung und einer zweiten Kommunikationssitzung aus einer gemeinsamen Kommunikationssitzung und Kommunikationssitzungs-Steuerungs-Server | |
DE69732221T2 (de) | Verfahren zum Anbieten von einem Dienst an Fernmeldenetzbenutzern | |
DE60312498T2 (de) | Wahlfähigster server in einer umgebung mit einer allgemeinen arbeit-warteschlange | |
DE69828544T2 (de) | Verfahren und Vorrichtung zum Nachrichtenaustausch zwischen mehreren Nachrichtenaustauschdiensten | |
DE10222361C2 (de) | Verfahren zum Betreiben eines verteilten Rechnernetzwerks umfassend mehrere verteilt angeordnete Rechner | |
DE10296696T5 (de) | Dynamische Verteilung von Teilnehmern bei einer zentralisierten Telefonkonferenz | |
EP0466948A1 (de) | Kommunikationssystem mit einem der zentralen Steuerung dienenden Multiprozessorsystem | |
EP1049013A2 (de) | Interprozesskommunikationssystem | |
WO2000054150A2 (de) | Verfahren zur nachrichtenübertragung zwischen einer einem ersten prozess zugewiesenen clientinstanz und wenigstens einer mindestens einem weiteren prozess zugewiesenen serverinstanz innerhalb eines verteilten systems | |
EP1977583B1 (de) | Verfahren zur Übermittlung einer Nachricht und Netzwerk | |
DE60016430T2 (de) | Verfahren und system zur übertragung einer meldungskette für datenbanken | |
DE60221118T2 (de) | Dienst applikationsarchitektur für dienstenanbieter von integrierende kommunikationsnetzwerken | |
DE60119553T2 (de) | Multiplexingeinheit, system und verfahren für die kommunikation über ein rechner-netzwerk | |
EP0782810B1 (de) | Verfahren und anordnung zur auflösung von leistungsmerkmal-interaktionen in einem kommunikationssystem | |
EP2815558A1 (de) | Übertragen von datenströmen zwischen einem endgerät und einem sicherheitsmodul | |
DE60036976T2 (de) | Verfahren zur Änderung eines Protokolls zwischen verteilten Objekten | |
DE10123822B4 (de) | Verfahren, System und maschinenlesbares Programmspeichergerät zur Überwachung einer Dienstverbindung zwischen einem Clientprozess und einem Serverprozess | |
DE60004161T2 (de) | Schnittstelle zu einem Netzwerkverwaltungssystem eines Kommunikationsnetzes | |
DE60036503T2 (de) | Verfahren zur Kommunikation zwischen Fernobjekten |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 00807384.8 Country of ref document: CN |
|
AK | Designated states |
Kind code of ref document: A2 Designated state(s): CN DE ID US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A2 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
AK | Designated states |
Kind code of ref document: A3 Designated state(s): CN DE ID US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A3 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
AK | Designated states |
Kind code of ref document: C2 Designated state(s): CN DE ID US |
|
AL | Designated countries for regional patents |
Kind code of ref document: C2 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
COP | Corrected version of pamphlet |
Free format text: PAGES 6-12, DESCRIPTION, REPLACED BY NEW PAGES 6-12; PAGES 1/2-2/2, DRAWINGS, REPLACED BY NEW PAGES 1/2-2/2; AFTER RECTIFICATION OF OBVIOUS ERRORS AS AUTHORIZED BY THE INTERNATIONAL SEARCHING AUTHORITY |
|
WWE | Wipo information: entry into national phase |
Ref document number: 09936385 Country of ref document: US |
|
REF | Corresponds to |
Ref document number: 10080578 Country of ref document: DE Date of ref document: 20020307 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 10080578 Country of ref document: DE |
|
122 | Ep: pct application non-entry in european phase |