CN1379876A - Method of distributing software updates in event-driven network - Google Patents
Method of distributing software updates in event-driven network Download PDFInfo
- Publication number
- CN1379876A CN1379876A CN 00814389 CN00814389A CN1379876A CN 1379876 A CN1379876 A CN 1379876A CN 00814389 CN00814389 CN 00814389 CN 00814389 A CN00814389 A CN 00814389A CN 1379876 A CN1379876 A CN 1379876A
- Authority
- CN
- China
- Prior art keywords
- new
- assembly
- network
- incident
- new policy
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
Abstract
A method of distributing software to handle previously unknown event types in a large multi-domain 'federation' network of decoupled, event-driven components. The components comprise producer components (10) which produce events and consumer components (25) which consume events to fulfill their specific roles in the federation. A producer component first determines a plurality of new events occurring in the network as a result of a new event type, and classifies the plurality of new events into at least one event-specific class. The producer component then pushes a single event (14) of an event-specific class into the network along with a new software strategy (13) for handling the event-specific class. The new strategy is distributed to the components in the network utilizing push technology (15). If the new strategy is applicable to a given component (31), the new strategy is cached (32) by the component and utilized to process events of the new type. If not applicable to the component, the new strategy is cached (34) by the component for use by downstream components. The process of distributing a strategy is then repeated for each event-specific class. The strategies are cached in the network components and are pushed to new components that bind to the network and subscribe to events of the new type. Thereafter, the new strategies are utilized by the components that received them to process events of the new type.
Description
Invention field
The present invention relates to software systems, more particularly, relate to divide in the large-scale multiple domain joint network (multi domain federationnetwork) at event driven assembly (component) be used in handle before the method for software upgrading of event type of the unknown.
Background of invention
Current, increasing software systems (for example telecommunication system) depend on the distributed architecture that its assembly is subjected to striding the control of a plurality of management domains.This industry is avoided the close-connected characteristic of each assembly seeking various ways, so that can upgrade or change the part of distributed system, and don't influences the other parts of system.
In large-scale telecommunication network management system (NMS), managed various network elements (element) As time goes on develops rapidly.In addition, be used for the cooperative control agreement of management of network element also because the rapid formation of the business partnership of telecommunication industry and breaking and frequent the change.These are true to make more to press for to design network element is upgraded or changed, and don't the method for the other parts of negative effect network.Yet, when being incorporated into the physical unit (as switch) of new type or logical unit (as software application) in the network that will manage, just may go wrong.Under best situation, existing mounted management software may not be handled new event type, so can lose the benefit of the information of the newtype that is generated by new equipment.In the worst case, introduce the instability that former undefined event type may cause the total system scope.In addition, relevant with new events type information might require some assemblies in the association (federation) treating these incidents in a different manner aspect incident storage, demonstration and the event correlation (correlation).
Problem to producing because introduce new events in the large-scale multiple domain joint network of event driven assembly has two main solutions at present.The first, network operator (operator) can upgrade all affected component softwares in the association simultaneously.In the large-scale association that is managed in real time by various cooperative management domains, this may be big, a unmanageable task of workload.Second kind of selection be the incident with newtype be designed to be with association at present known event type backward compatibility.Yet this way also has shortcoming.The first, new each must also have possible unwanted function in each older generation for event type.The second, to the requirement of backwards compatibility, may limit the function that a new generation may have.The 3rd, in expensive new each after generation of wanting backward compatibility that time-consumingly designed, in each older generation, may withdraw from the installation of a new generation after, makes thus to obtaining the effort that backwards compatibility carries out and spending unnecessary.
In order to overcome the shortcoming of existing solution, a kind of like this distribution software method for updating is preferably arranged, this method does not need the operator side by side to upgrade all affected networking components, do not need expensive ground, sometimes new event type is designed unnecessaryly with the process of current known event type backward compatibility.The invention provides a kind of like this method.
Summary of the invention
On the one hand, the present invention is a kind of method of distribution software, is used for handling the new events type at the network decoupling with a plurality of production and consumption incidents, event driven assembly.The step that this method comprises is, the new software strategy that will be used to handle the new events type pushes (push into) network from the generator assembly, and adopts and push the assembly of technology (push technology) in network and distribute New Policy.Distribute the step of New Policy can comprise that the screening function that utilization pushes in the technology distributes New Policy selectively, whether be applicable to each assembly in the network to determine New Policy, and shift this strategy onto those assemblies that New Policy is suitable for.
On the other hand, method of the present invention can adopt and not adopt the publication of screening and push (publish and push) technology in each assembly.In addition, the present invention also can only be applied to upgrade existing assembly.In this case, the step that this method comprises is, the new software strategy that will be used for handling the new events type is shifted consumer (consumer) assembly of network onto from the producer (producer) assembly, and adopts New Policy to handle the incident of newtype by existing assembly.If this method also will be used for new assembly, then this method also comprises the steps: the assembly high speed buffer memory New Policy in network, determine when that new consumer's assembly is connected to the incident of network and subscription (subscribe to) new events type, and New Policy is pushed New Parent.New Policy is used for handling the incident of newtype then by New Parent.
On the other hand, the step that this method comprises is, the new software type that will be used to handle the new events type pushes network from producer component, and utilizes the technology that pushes to distribute the assembly of New Policy in the network selectively.Determine whether New Policy is applicable to each assembly in the network, if determine that New Policy is applicable to given assembly, New Policy is just got up for the locking assembly high-speed cache by this and should be used for handling the incident of newtype to locking assembly.If determine that New Policy is not suitable for given assembly, this strategy is just got up for the locking assembly high-speed cache by this, for being used by downstream components.When new consumer's assembly is connected to network and subscribes to the incident of new events type, New Policy is pushed New Parent.
This method also can allow producer component at first determine a plurality of new events that occur as the result of new events type at the beginning in network.Producer component is categorized into the specific class of at least one incident with these a plurality of new events.A single incident of the class that producer component is specific with first incident then pushes network together with first New Policy that is used to handle the specific class of this first incident.Utilization pushes technology this first New Policy optionally is assigned to assembly in the network.If this first New Policy is applicable to that certain gives locking assembly, this New Policy is just got up by this assembly high-speed cache and is used to handle the incident of this newtype.If be not suitable for this assembly, this first New Policy is just got up for being used by downstream components by this assembly high-speed cache.Then the specific class of each incident is repeated the process of this allocation strategy.Each strategy is cached in the networking component, and shifts the New Parent of the incident that is connected to network and subscribes to newtype onto.Then, utilize New Policy to handle the incident of newtype by the assembly that receives New Policy.
Brief description
Consult the following drawings in conjunction with this instructions, can understand the present invention better, numerous purposes of the present invention and advantage will become apparent for those skilled in the art.In the accompanying drawing:
Fig. 1 is the process flow diagram that is illustrated in the step of being carried out by producer component in the most preferred embodiment of method of the present invention;
Fig. 2 is the process flow diagram that is illustrated in the step of being carried out by the technology that pushes in the most preferred embodiment of method of the present invention;
Fig. 3 is the process flow diagram that is illustrated in the step of being carried out by consumer's assembly in the most preferred embodiment of method of the present invention;
Fig. 4 is the example scenarios of new events type is introduced in expression in joint network according to a thought of the present invention synoptic diagram.
Embodiment describes in detail
The present invention describe a kind of in large-scale multiple domain joint network decoupling, event driven assembly of management, distribution and processing events, divide be used in handle before the method for software of event type of the unknown.A kind of method of network of setting up the assembly of such decoupling is to use " publish and push " technology.Information producer's published information also pushes it in network.One or more information consumer are to network registry, and network just information is shifted information consumer onto.In this example, information producer and information consumer be stored-and-transmit medium (store-and-forwardmedium) decoupling.The producer does not need to know the consumer, and the producer's state is independent of consumer's state (vice versa).
In the particular condition of telecommunication system, information can be network event, such as network alarming, network performance data, Network Finance data or the like.The information producer can be a network element, and information consumer can be communication network (NMS).
So, publish and push the association that technology helps to construct distributed event driven assembly.In association, each assembly is produced and/or the consumption incident, to finish the specific role (role) in association.These assemblies some can gateway, their receive the information sent by device or other system and information are translated into incident.They push network to incident then.Other is subscribed to network receiving the interested assembly of these event types, so that these incidents will be pushed to them in the future.These assemblies are after the reception incident, and processing events can generate new incident according to handled information then, and new incident also is pushed into network.
In the method for the invention, software upgrading is to distribute in association automatically.The assembly of distribution of information event type (producer) is responsible for providing consumer's assembly to be used to handle the suitable software (hereinafter referred to as strategy) of new events type.Strategy generally is stored in the incident, can be the brand-new code that is used to handle the incident of newtype, also can be the patch of existing code.When having tactful incident when consumer's assembly is received, the consumer determines whether this strategy is applicable to it.If be suitable for, this strategy just is mounted, then just according to the behavior of the informational influence consumer assembly that carries in the new events type.
Fig. 1 is the process flow diagram that is illustrated in the step of being carried out by producer component (producer) 10 in the most preferred embodiment of method of the present invention.The a plurality of producers that represented by producer 1-N can be the step of different incident execution graphs 1.In step 11, the producer creates new events.The producer can determine with its knowledge to the component type in the association will be by introducing a plurality of new events that new event type is generated in association.The producer is categorized into the specific class of incident with new events, and determines the corresponding strategies of the class that each incident is specific.Required strategy number is relevant with the role's that new events will influence number.In step 12, the producer determines whether that the strategy of incident has been pushed into network.If strategy is not pushed into, this method is just transferred to step 13, with policy store in incident.In step 14, shift incident onto the technology of pushing 15, supply in network, to distribute, and no matter whether the consumer of this event type is arranged.Ideally, the class of carrying this incident will comprise that one is designed the issue number (release number) of the form of the event type of producing to be processed corresponding to it.Be pushed into if determine the strategy of incident in step 12, then incident is pushed in step 14, and does not have strategy.
Fig. 2 is expression process flow diagram by the step of the technology that pushes the most preferred embodiment of method of the present invention 15 execution when receive an incident from the producer 10.In step 21, determine to push whether screening function is arranged in the technology.If have, determine whether to want filter events in step 22.If incident is screened and abandons in step 23.If there is not screening function, perhaps do not want filter events, then this method is transferred to step 24, shifts incident onto consumer's assembly (consumer) 25.
Have the pushing in the technology of screening function, push in the technology screening washer selectively the consumer's assembly in association distribute New Policy.Like this, be used in the network inter-component communication the screening function of the technology that pushes determine whether that given strategy is applicable to given assembly.For example, if certain screening washer is inserted the upstream from specific components, and this screening washer stops the distribution of specific policy, and then this assembly is not just known this strategy, is removed up to this screening washer.
Some publication and the technology that pushes do not adopt screening function.If adopt such technology, strategy just is pulled to all existing assemblies.After strategy was assigned with, the consumer utilized New Policy that the incident that the general strategy that provides to them when installing is handled newtype is provided.
Fig. 3 is expression process flow diagram by the step of 25 execution of the consumer's assembly the most preferred embodiment of method of the present invention when the incident that has strategy arrives from pushing technology 15.In step 31, determine whether this strategy is applicable to the reception consumer.If be suitable for, the consumer installs this strategy in step 32, handles the incident of newtype then at this strategy of 33 usefulness.The consumer should get up by the strategy high-speed cache in step 34 then.If determine that in step 31 this strategy is not suitable for the reception consumer, this method is just directly transferred to step 34, should get up by the strategy high-speed cache, is used for being assigned to subsequently the downstream components that needs it.
In step 35, determine whether consumer 25 also is the producer of the incident of downstream components.If the incident that then will have strategy is shifted the technology of pushing 15 onto, for the downstream components that is assigned in the network.If the consumer is not the producer, this method is just transferred to step 36, and the processing in the consumer stops at this.
The strategy that is assigned with is realized the interface based on the role.Each role that assembly can be played the part of is associated with an abstraction interface.For example, the assembly of being responsible for canned data in database can use a strategy of realizing the interface of an exclusive key that returns (stored) given incident.This key is normally specific to an event type.The producer of new events type should produce a strategy suitable, that can create key according to the fresh information in this new events type then.If new consumer is connected in the association and subscribes to the incident of this newtype, association just arrives this consumer with this suitable policy download in its initial download, and then, this New Policy is used for handling the incident of this newtype by this new consumer.
Fig. 4 is the example scenarios of new events type is introduced in expression in joint network according to a thought of the present invention synoptic diagram.Assembly P1 41 and P2 42 are respectively the producer of incident 43 and 44 in association.P1 and P2 provide the strategy that is associated in the incident of being stored in these incidents, no matter in the association whether the consumer who needs these event types is arranged.Incident and strategy are provided to consumer C1 45 by pushing technology (PT) 15.After utilizing PT 15 forwarding incidents, incident and strategy are cached among the C1.
In the situation of Fig. 4, producer P2 is connected to new physical unit 51, determines a strategy that is associated with this incident.Shift new events and New Policy onto consumer C1 in aforesaid mode by association, got up by high-speed cache at this.Shift New Policy onto consumer C3 and C4, get up at this high-speed cache.Consumer C3 in this example determines that this New Policy is inapplicable, therefore abandons this New Policy.Consumer C4 determines that this New Policy is suitable for it, and therefore this New Policy is installed.C4 can provide with the software of physical unit 51 with this New Policy then and be connected, and perhaps communicates by letter with P2.
If new consumer C5 52 is connected to association and subscribes to this new events, C1 sends this New Policy to C5.Consumer C5 gets up to utilize then this New Policy with the New Policy high-speed cache when it receives the incident of newtype.
Believe the explanation according to the front, operation of the present invention and structure will be conspicuous.Although shown in and illustrated method, preparation and system be characterized as preferably, obvious, can do various modifications and change to it under the situation of the scope of the present invention that in not departing from following claim, defines.
Claims (10)
1. a distribution is used for having the method that network a plurality of decouplings, event driven assembly is handled the software of new events type, and described assembly is the producer of incident and the consumer of incident, and the step that this method comprises is:
The new software strategy that will be used to handle the new events type pushes network from producer component; With
Employing pushes the assembly distribution New Policy of technology in network.
2. the method for claim 1 is characterised in that, utilizes the step that pushes technology distribution New Policy to comprise that utilization pushes technology and distributes New Policy selectively.
3. the method for claim 2 is characterised in that, utilizes the technology that pushes to distribute the step that the step of New Policy comprises selectively to be:
Determine whether New Policy is applicable to each assembly in the network; With
Shift this New Policy onto those assemblies that New Policy is suitable for.
4. the method for claim 1 is characterised in that, the step that further comprises is:
Determine whether New Policy is applicable to each assembly in the network;
If determine that New Policy is applicable to given assembly, New Policy is just got up for the locking assembly high-speed cache by this and should be used for handling the incident of newtype to locking assembly; With
If determine that New Policy is not suitable for given assembly, this strategy is just got up for the locking assembly high-speed cache by this, for being used by downstream components.
5. the method for claim 1 is characterised in that, the step that further comprises is:
Determine when that new consumer's assembly is connected to network and subscribes to the incident of new events type; With
New Policy is pushed this New Parent.
6. a distribution is used for having the method that network a plurality of decouplings, event driven assembly is handled the software of new events type, and described assembly is the producer of incident and the consumer of incident, and the step that this method comprises is:
The new software strategy that will be used to handle the new events type pushes network from producer component;
Assembly in network is distributed this New Policy selectively, and the step that described distributing step comprises is:
Determine whether New Policy is applicable to each assembly in the network; With
Utilization pushes technology and shifts this New Policy onto those assemblies that New Policy is suitable for;
Determine when that new consumer's assembly is connected to network and subscribes to the incident of new events type; With
New Policy is pushed this New Parent.
7. a distribution is used for having the method that network a plurality of decouplings, event driven assembly is handled the software of new events type, and described assembly is the producer of incident and the consumer of incident, and the step that this method comprises is:
The new software strategy that will be used to handle the new events type pushes network from producer component;
Utilization pushes the assembly of technology in network and distributes this New Policy;
Determine whether New Policy is applicable to each assembly in the network;
If determine that New Policy is applicable to given assembly, New Policy is just got up for the locking assembly high-speed cache by this and should be used for handling the incident of newtype to locking assembly;
If determine that New Policy is not suitable for given assembly, this strategy is just got up for the locking assembly high-speed cache by this, for being used by downstream components.
Determine when that new consumer's assembly is connected to network and subscribes to the incident of new events type; With
New Policy is pushed this New Parent.
8. a distribution is used for having the method that network a plurality of decouplings, event driven assembly is handled the software of new events type, and described assembly is the producer of incident and the consumer of incident, and the step that this method comprises is:
The new software strategy that will be used for handling the new events type is shifted consumer's assembly onto from the producer component of network; With
Utilize this New Policy to handle the incident of newtype by existing assembly.
9. the method for claim 8 is characterised in that the step that further comprises is:
By the assembly in the network this New Policy high-speed cache is got up;
Determine when that new consumer's assembly is connected to network and subscribes to the incident of new events type;
New Policy is pushed this New Parent; With
Utilize this New Policy to handle the incident of newtype by this New Parent.
10. a distribution is used for having the method that network a plurality of decouplings, event driven assembly is handled the software of new events type, described assembly comprises consumer's assembly of producer component and at least one consumption incident of a production incident, and the step that this method comprises is:
(A) at first determine a plurality of new events of in network, occurring as the result of new events type by producer component;
(B) it is specific by producer component these a plurality of new events to be categorized at least one incident
Class;
(C) a single incident of the class that first incident is specific pushes network together with the first new software strategy that is used to handle the specific class of this first incident;
(D) utilize the technology that pushes that this first New Policy is distributed to each assembly in the network;
(E) determine whether this first New Policy is applicable to each assembly in the network;
(F) determine that this first New Policy is applicable to behind the locking assembly, this New Policy is just got up by this assembly high-speed cache and is used to handle the incident of this newtype by this assembly;
(G) determine that this first New Policy is not suitable for to behind the locking assembly, this first New Policy is just got up for being used by downstream components by this assembly high-speed cache;
(H) determine whether the specific class of this incident is last class of being classified by producer component in step (B);
(I) the specific class of each other incident in step (B), classifying by producer component, repeating step (C) is distributed the software strategy corresponding to the specific class of each incident thus to (H);
(J) utilize New Policy to handle the incident of newtype by each assembly.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US37517799A | 1999-08-16 | 1999-08-16 | |
| US09/375,177 | 1999-08-16 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1379876A true CN1379876A (en) | 2002-11-13 |
| CN1153137C CN1153137C (en) | 2004-06-09 |
Family
ID=23479808
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB008143897A Expired - Fee Related CN1153137C (en) | 1999-08-16 | 2000-08-15 | Method of distributing software updates in event-driven network |
Country Status (5)
| Country | Link |
|---|---|
| EP (1) | EP1277111A1 (en) |
| CN (1) | CN1153137C (en) |
| AU (1) | AU768653B2 (en) |
| CA (1) | CA2402254A1 (en) |
| WO (1) | WO2001013226A1 (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100421070C (en) * | 2005-03-30 | 2008-09-24 | 国际商业机器公司 | Method and system for managing dynamic configuration data |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7853609B2 (en) | 2004-03-12 | 2010-12-14 | Microsoft Corporation | Update distribution system architecture and method for distributing software |
| US8612997B2 (en) | 2008-01-15 | 2013-12-17 | International Business Machines Corporation | Event-driven component integration framework for implementing distributed systems |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5321837A (en) * | 1991-10-11 | 1994-06-14 | International Business Machines Corporation | Event handling mechanism having a process and an action association process |
| DE69625652T2 (en) * | 1995-08-18 | 2003-09-18 | Ibm | Event Management Services |
| US5862325A (en) * | 1996-02-29 | 1999-01-19 | Intermind Corporation | Computer-based communication system and method using metadata defining a control structure |
| US5933645A (en) * | 1996-03-19 | 1999-08-03 | Oracle Corporation | Non-invasive extensibility of software applications |
-
2000
- 2000-08-15 AU AU68825/00A patent/AU768653B2/en not_active Ceased
- 2000-08-15 CA CA002402254A patent/CA2402254A1/en not_active Abandoned
- 2000-08-15 WO PCT/SE2000/001581 patent/WO2001013226A1/en not_active Application Discontinuation
- 2000-08-15 CN CNB008143897A patent/CN1153137C/en not_active Expired - Fee Related
- 2000-08-15 EP EP00957171A patent/EP1277111A1/en not_active Withdrawn
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100421070C (en) * | 2005-03-30 | 2008-09-24 | 国际商业机器公司 | Method and system for managing dynamic configuration data |
Also Published As
| Publication number | Publication date |
|---|---|
| CA2402254A1 (en) | 2001-02-22 |
| AU768653B2 (en) | 2003-12-18 |
| WO2001013226A1 (en) | 2001-02-22 |
| AU6882500A (en) | 2001-03-13 |
| CN1153137C (en) | 2004-06-09 |
| EP1277111A1 (en) | 2003-01-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7360208B2 (en) | Rolling upgrade of distributed software with automatic completion | |
| US6298378B1 (en) | Event distribution system for computer network management architecture | |
| US7412493B2 (en) | Publish/subscribe messaging system | |
| MXPA04002480A (en) | Network printer connection update scheme for printer clients. | |
| US20060070084A1 (en) | Method and apparatus for creating templates | |
| US20080155517A1 (en) | Generating rule packs for monitoring computer systems | |
| AU2002336667A1 (en) | Data synchronization | |
| CN101739745A (en) | Queuing processing device and processing method thereof and queuing machine | |
| US20080126987A1 (en) | Graphical representation of compatible workflow steps | |
| CN1866283B (en) | System and method for implementing regular system triggering | |
| US6167451A (en) | Multiple push protocol unifying system | |
| IL127789A (en) | Publish and subscribe data processing apparatus, method and computer program product | |
| US20070156878A1 (en) | System and method for managing workflow execution in a distributed system | |
| Barga et al. | Event correlation and pattern detection in CEDR | |
| EP1695217A2 (en) | Management system and method for managing distributed resources | |
| EP0961452A2 (en) | Publish & subscribe data processing apparatus, method and computer program product with use of a stream to distribute administrative and configuration information | |
| US20040267927A1 (en) | Methods, systems and program products for delivery of web services using categorical contracts | |
| CN1379876A (en) | Method of distributing software updates in event-driven network | |
| US8121965B2 (en) | Updating an engine using a description language | |
| Eugster et al. | Event systems. How to have your cake and eat it too | |
| WO1999034557A1 (en) | Method and system for software version management in a network management system | |
| US7831958B2 (en) | Systems and methods for distributing updated information | |
| US7624423B1 (en) | Systems and methods for software distribution using distribution policies | |
| Detmold et al. | Middleware for video surveillance networks | |
| JP2001236310A (en) | Device and method for diverse issue and quotation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C06 | Publication | ||
| PB01 | Publication | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C19 | Lapse of patent right due to non-payment of the annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |