AU6882500A

AU6882500A - Method of distributing software updates in an event-driven network

Info

Publication number: AU6882500A
Application number: AU68825/00A
Authority: AU
Inventors: Nicolas Gosselin; Fergus Kelledy; David O'flanagan; Edwin Tse
Original assignee: Telefonaktiebolaget LM Ericsson AB
Current assignee: Telefonaktiebolaget LM Ericsson AB
Priority date: 1999-08-16
Filing date: 2000-08-15
Publication date: 2001-03-13
Anticipated expiration: 2020-08-15
Also published as: CA2402254A1; AU768653B2; CN1153137C; CN1379876A; WO2001013226A1; EP1277111A1

Description

WO 01/13226 PCT/SE00/01581 METHOD OF DISTRIBUTING SOFTWARE UPDATES IN AN EVENT-DRIVEN NETWORK BACKGROUND OF THE INVENTION 5 Technical Field of the Invention This invention relates to software systems, and more particularly, to a method of distributing software updates to handle previously unknown event types in a large multi-domain federation network of event-driven components. Description of Related Art 10 Currently, an increasing number of software systems (for example, telecommunication systems) rely on distributed architectures whose components are controlled across multiple administrative domains. The industry is looking for ways to avoid tightly coupled characteristics of components so that portions of the distributed system can be upgraded or changed without impact on other parts of the 15 system. In large telecommunications Network Management Systems (NMSs), various network elements under management are evolving rapidly over time. In addition, cooperative management agreements for the management ofnetwork elements are also changing frequently due to the rapid making and breaking of business partnerships in 20 the telecommunications industry. These facts make it more critical that methods be devised to make upgrades or changes to network elements without adversely impacting other parts of the network. However, when a physical device (like a switch) or a logical device (like a software application) of a new type is brought into the network to be managed, problems may arise. At best, the existing installed 25 management software may not be able to process the new event types, and the benefits of the new types of information generated by the new device are lost. At worst, the introduction ofpreviously undefined event types may introduce instability throughout the system. Furthermore, it is likely that information related to the new event types may require some components in the federation to behave differently toward those 30 events in terms of event storage, display, and event correlation.

WO 01/13226 PCT/SE00/01581 -2 There are currently two major solutions to the problems caused by the introduction of new events into large multi-domain federation networks of event driven components. First, the network operator may upgrade all of the affected software components in the federation at the same time. In a large federation which 5 is administered by various cooperative management domains in real-time, this can be a large and difficult task to administer. The second option is to design new event types to be backward-compatible with event types currently known in the federation. This approach, however, also has disadvantages. First, the new generations of event types must also carry functionality from older generations that may not be needed. Second, 10 the requirement to be backward-compatible may limit the capabilities that the new generation can have. Third, after costly and time-consuming design of new generations to be backward-compatible, the older generation may be retired after installation of the new generation, thus making the effort and expense to achieve backward-compatibility unnecessary. 15 In order to overcome the disadvantage of existing solutions, it would be advantageous to have a method ofdistributing software updates which does not require an operator to simultaneously update of all of the affected network components, and does not require the costly and sometimes unnecessary process of designing new event types to be backward-compatible with currently known event types. The present 20 invention provides such a method. SUMMARY OF THE INVENTION In one aspect, the present invention is a method of distributing software to handle a new event type in a network having a plurality of decoupled, event-driven 25 components which produce and consume events. The method includes the steps of pushing a new software strategy for handling a new event type from a producer component into the network, and utilizing push technology to distribute the new strategy to the components in the network. The step of distributing the new strategy may include selectively distributing the new strategy utilizing filtering capabilities in 30 the push technology to determine whether the new strategy is applicable to each component in the network, and pushing the new strategy to those components for WO 01/13226 PCT/SE00/01581 -3 which the new strategy is applicable. In another aspect, the method ofthe present invention may utilize a publish and push technology that does not utilize filtering in the individual components. Additionally, the invention may be applied only to update existing components. In 5 this case, the method comprises the steps of pushing a new software strategy for handling anew event type from a producer component to consumer components in the network, and utilizing the new strategy by the existing components to process events of the new type. If the method is to be utilized for new components as well, then the method also includes the steps of caching the new strategy in the components in the 10 network, determining when a new consumer component binds into the network and subscribes to events of the new event type, and pushing the new strategy to the new component. The new strategy is then utilized by the new component to process events of the new type. In another aspect, the method includes the steps of pushing a new software 15 strategy for handling a new event type from a producer component into the network, and utilizing push technology to selectively distribute the new strategy to the components in the network. It is determined whether the new strategy is applicable to each component in the network, and upon determining that the new strategy is applicable to a given component, the strategy is cached by the given component and 20 utilized by the given component to process events of the new type. Upon determining that the new strategy is not applicable to a given component, the strategy is cached by the given component for use by downstream components. When a new consumer component binds into the network and subscribes to events of the new event type, the new strategy is pushed to the new component. 25 The method may also begin by having the producer component first determine a plurality of new events occurring in the network as a result of a new event type. The producer component classifies the plurality of new events into at least one event specific class. The producer component then pushes into the network, a single event of a first event-specific class along with a first new software strategy for handling the 30 first event-specific class. The first new strategy is selectively distributed to the components in the network utilizing push technology. If the first new strategy is WO 01/13226 PCT/SE00/01581 -4 applicable to a given component, the first new strategy is cached by the component and utilized to process events of the new type. If not applicable to the component, the first new strategy is cached by the component for use by downstream components. The process of distributing a strategy is then repeated for each event-specific class. 5 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. 10 BRIEF DESCRIPTION OF THE DRAWINGS The invention will be better understood and its numerous objects and advantages will become more apparent to those skilled in the art by reference to the following drawings, in conjunction with the accompanying specification, in which: FIG. 1 is a flow chart illustrating the steps performed by a producer component 15 in the preferred embodiment of the method of the present invention; FIG. 2 is a flow chart illustrating the steps performed by the push technology in the preferred embodiment of the method of the present invention; FIG. 3 is a flow chart illustrating the steps performed by a consumer component in the preferred embodiment of the method of the present invention; and 20 FIG. 4 is an illustrative drawing of an exemplary scenario showing the introduction of a new event type in a federation network according to the teachings of the present invention. DETAILED DESCRIPTION OF EMBODIMENTS 25 The present invention describes a method of distributing software to handle previously unknown event types in a large multi-domain "federation" network of decoupled, event-driven components which manage, distribute, and process events. One way to build such a decoupled-component network is to use "publish and push" technologies. An information producer publishes the information and pushes it into 30 the network. One or more information consumer(s) registers itself with the network, and the network pushes information to the information consumer. In this paradigm, WO 01/13226 PCT/SE00/01581 -5 the information producer and the information consumer are decoupled by a store-and forward medium. The producer need not be aware of the consumer(s), and states of the producers are independent from the states of the consumers (and vice versa). In the specific case of telecommunication systems, the information may be 5 network events such as network alarms, network performance data, network accounting data, etc. Information producers may be network elements, and information consumers may be telecommunications Network Management Systems (NMSs). Thus, publish and push technologies facilitate the construction of a federation 10 of distributed, event-driven components. In the federation, each component produces and/or consumes events to fulfill its specific role in the federation. Some of these components may be gateways that receive information emitted by devices or other systems, and translate the information into events. Then, they push the events into the network. Other components, interested in receiving those event types, subscribe to the 15 network so that those events will be pushed to them in the future. These components, after receiving the events, process them and may generate new events based on the processed information which are also pushed into the network. In the method of the present invention, software updates are automatically distributed in the federation. Components issuing new event types (producers) are 20 responsible for supplying consumer components with appropriate software (hereinafter called Strategy) for handling the new event types. The Strategy, which is normally stored within the event, may be entirely new code for handling events of the new type, or it may be a patch for existing code. When the event with Strategy is received at a consumer component, the consumer decides whether the strategy is applicable to it. 25 If so, the Strategy is installed and thereafter affects the behavior of the consumer component according to information carried in the new event type. FIG. 1 is a flow chart illustrating the steps performed by a producer component (Producer) 10 in the preferred embodiment of the method of the present invention. A plurality of Producers, represented as Producers 1-N may be performing the steps of 30 FIG. 1 for different events. At step 11, the Producer creates a new event. The Producer may use its knowledge of component types in the federation to determine a WO 01/13226 PCT/SE00/01581 -6 plurality of new events that will be generated by the introduction of a new event type in the federation. The Producer classifies the new events into event-specific classes, and determines an associated Strategy for each event-specific class. The number of required Strategies depends on the number of roles anew event will affect. At step 12, 5 the Producer determines whether or not the Strategy for the event has already been pushed into the network. If the Strategy has not been pushed, the method moves to step 13 where the strategy is stored in the event. At step 14, the event is then pushed to the push technology 15 for distribution in the network regardless of whether there are consumers for the event type or not. Ideally, the event conveying the class should 10 include a release number corresponding to the format of the produced event type it is designed to handle. If it is determined at step 12 that the Strategy for the event has already been pushed, then the event is pushed at step 14 without Strategy. FIG. 2 is a flow chart illustrating the steps performed by the push technology 15 in the preferred embodiment of the method of the present invention when an event 15 is received from a Producer 10. At step 21, it is determined whether or not there is a filtering capability in the push technology. If so, it is determined at 22 whether or not the event is to be filtered. If so, the event is filtered out and discarded at 23. If there are no filtering capabilities, or the event is not to be filtered, the method moves to step 24 where the event is pushed to consumer components (Consumers) 25. 20 In push technology with filtering capabilities, filters in the push technology selectively distribute the new Strategy to consumer components in the federation. Thus, the filtering capabilities of the push technology being utilized in the network for inter-component communications determine whether or not a given Strategy is applicable to a given component. For example, if a filter is inserted upstream from a 25 particular component, and the filter blocks the distribution of a particular Strategy, then the component has no knowledge of the Strategy until the filter is removed. Some publish and push technologies do not utilize filtering; if such a technology is utilized, the Strategy is pushed to all of the existing components. After the Strategy is distributed, the consumers utilize the new Strategy to process events of 30 the new type instead of the generic Strategy they were provided with at installation. FIG. 3 is a flow chart illustrating the steps performed by a consumer WO 01/13226 PCT/SE00/01581 -7 component 25 in the preferred embodiment of the method of the present invention when an event with Strategy arrives from the push technology 15. At step 31, it is determined whether or not the Strategy is applicable for the receiving Consumer. If so, the Consumer installs the Strategy at 32 and then uses the Strategy to process 5 events of the new type at 33. The Consumer then caches the Strategy at step 34. If it is determined at step 31 that the Strategy is not applicable for the receiving Consumer, the method moves directly to step 34 and caches the Strategy for subsequent distribution to downstream components that require it. At step 35, it is determined whether or not the Consumer 25 is also a Producer 10 of events for downstream components. If so, the event with Strategy is then pushed to the push technology 15 for distribution to downstream components in the network. If the Consumer is not a Producer, the method moves to step 36 where the processing within the Consumer stops. The distributed Strategies implement a role-based interface. Each role a 15 component can play is associated with an abstract interface. For example, a component responsible for storing information in a database may use a Strategy which implements an interface that returns a unique key for a given event (to be stored). That key is usually specific to one event type. A producer of a new event type should then produce an appropriate Strategy that can create a key based on the new 20 information in the new event type. If a new consumer binds into the federation and subscribes for events of the new type, the federation downloads the appropriate Strategy to the consumer in its initial download, and the new Strategy is then utilized by the new consumer to process events of the new type. FIG. 4 is an illustrative drawing of an exemplary scenario showing the 25 introduction of a new event type in a federation network according to the teachings of the present invention. Components P1 41 and P2 42 are Producers of events 43 and 44, respectively, in the federation. Along with the events, P1 and P2 provide associated Strategies stored in the events regardless of whether there are consumers in the federation for those event types or not. The events and Strategies are provided 30 via push technology (PT) 15 to consumer C1 45. After forwarding the events utilizing PT 15, the events and Strategies are cached in C1.

WO 01/13226 PCT/SE00/01581 -8 PT 15 then pushes the events to consumers C3 46 and C4 47. In this example, C3 is a component which correlates alarm messages it receives and issues correlation events 48 back into the federation through PT 15. Likewise, C4 is exemplified as a component which displays events to an operator through a user interface, and provides 5 the operator with a software connection 49 to a physical device 51 connected to P2. In the scenario of FIG. 4, Producer P2 connects to the new physical device 51, and determines a Strategy associated with this event. The new event and the new Strategy are pushed through the federation, as described above, to consumer Cl where they are cached. The new Strategy is pushed to consumers C3 and C4 where it is 10 cached. Consumer C3 in this example determines that the new Strategy is not applicable, and therefore disregards the new Strategy. Consumer C4 determines that the new Strategy is applicable to it, and installs the new Strategy. C4 may then use the new Strategy to provide the software connection 49 to the physical device 51, or to communicate with P2. 15 If a new consumer C5 52 binds to the federation and subscribes to the new event, Cl sends the new Strategy to C5. Consumer C5 caches the new Strategy and thereafter utilizes the new Strategy when it receives events of the new type. It is thus believed that the operation and construction of the present invention 20 will be apparent from the foregoing description. While the method, apparatus and system shown and described has been characterized as being preferred, it will be readily apparent that various changes and modifications could be made therein without departing from the scope of the invention as defined in the following claims. 25

Claims

1. A method of distributing software to handle a new event type in a network having a plurality of decoupled, event-driven components, said components 5 being producers of events and consumers of events, said method comprising the steps of: pushing from a producer component into the network, a new software strategy for handling a new event type; and utilizing push technology to distribute the new strategy to the components in 10 the network.

2. The method of claim 1 wherein the step of utilizing push technology to distribute the new strategy includes utilizing push technology to selectively distribute the new strategy. 15

3. The method of claim 2 wherein the step of utilizing push technology to selectively distribute the new strategy includes the steps of: determining whether the new strategy is applicable to each component in the network; and 20 pushing the new strategy to those components for which the new strategy is applicable.

4. The method of claim 1 further comprising the steps of: determining whether the new strategy is applicable to each component in the 25 network; upon determining that the new strategy is applicable to a given component, caching the strategy by the given component and utilizing the new strategy by the given component to process events of the new type; and upon determining that the new strategy is not applicable to a given component, 30 caching the strategy by the given component for use by downstream components. WO 01/13226 PCT/SE00/01581 -10

5. The method of claim 1 further comprising the steps of: determining when a new consumer component binds into the network and subscribes to events of the new event type; and pushing the new strategy to the new component. 5

6. A method of distributing software to handle a new event type in a network having a plurality of decoupled, event-driven components, said components being producers of events and consumers of events, said method comprising the steps of: 10 pushing from a producer component into the network, a new software strategy for handling a new event type; selectively distributing the new strategy to the components in the network, said distributing step including the steps of: determining whether the new strategy is applicable to each component 15 in the network; and utilizing push technology to push the new strategy to those components for which the new strategy is applicable; determining when a new consumer component binds into the network and subscribes to events of the new event type; and 20 pushing the new strategy to the new component.

7. A method of distributing software to handle a new event type in a network having a plurality of decoupled, event-driven components, said components being producers of events and consumers of events, said method comprising the steps 25 of: pushing from a producer component into the network, a new software strategy for handling a new event type; utilizing push technology to distribute the new strategy to the components in the network; 30 determining whether the new strategy is applicable to each component in the network; WO 01/13226 PCT/SE00/01581 -11 upon determining that the new strategy is applicable to a given component, caching the strategy by the given component and utilizing the new strategy by the given component to process events of the new type; upon determining that the new strategy is not applicable to a given component, 5 caching the strategy by the given component for use by downstream components; determining when a new consumer component binds into the network and subscribes to events of the new event type; and pushing the new strategy to the new component. 10

8. A method of distributing software to handle a new event type in a network having a plurality of decoupled, event-driven components, said components being producers of events and consumers of events, said method comprising the steps of: pushing a new software strategy for handling a new event type from a producer 15 component to consumer components in the network; and utilizing the new strategy by the existing components to process events of the new type.

9. The method of claim 8 further comprising the steps of: 20 caching the new strategy by the components in the network; determining when a new consumer component binds into the network and subscribes to events of the new event type; pushing the new strategy to the new component; and utilizing the new strategy by the new component to process events of the new 25 type.

10. A method of distributing software to handle a new event type in a network having a plurality of decoupled, event-driven components, said components including a producer component which produces events and at least one consumer 30 component which consumes events, said method comprising the steps of: (A) determining by the producer component, a plurality of new events WO 01/13226 PCT/SE00/01581 -12 occurring in the network as a result of the new event type; (B) classifying by the producer component, the plurality of new events into at least one event-specific class; (C) pushing from the producer component into the network, a single event of 5 a first event-specific class along with a first new software strategy for handling the first event-specific class; (D) utilizing push technology to distribute the first new strategy to the components in the network; (E) determining whether the first new strategy is applicable to each component 10 in the network; (F) upon determining that the first new strategy is applicable to a given component, caching the first new strategy by the given component and utilizing the first new strategy by the given component to process events of the new type; (G) upon determining that the first new strategy is not applicable to a given 15 component, caching the first new strategy by the given component for use by downstream components; (H) determining whether the event-specific class is the last class classified by the producer component in step (B); (I) repeating steps (C) through (H) for each additional event-specific class 20 classified by the producer component in step (B), thereby distributing software strategies corresponding to each event-specific class; and (J) utilizing the new strategies by the components to process events of the new type. 25